Ryan,
I have no idea why this is occurring. Could you provide more information? Such as when you say everything was working then failed, what was working? Jogging or GCode motion or sitting idle?
Do you have the Keling wired up to the Aux1 connector?
Possibilities I can think of might be:
#1 - We don't have any protection against jogging on the MPG while GCode is running. To eliminate this as a possibility try re-assigning the A B Quadrature inputs to 46 and 47 (The KFlop LEDS) and see if a problem ever occurs (of course you wont be able to test jogging with the MPG).
#2 - I just realized we are connecting 5V outputs to 3.3V inputs (with an internal 150 ohm pull down). I doubt if this is a problem unless the MPG is driving the signals hard above 3.9V (because the 3.3V inputs are diode clamped to the 3.3V power rail). Please check the outputs to see what voltage they rise to. The ideal test would be disconnected from the KFlop and with a 150ohm pulldown resistor. Or add 50 ohm series resistors to be safe.
#3 - Possibly just the long MPG cable picking up noise and injecting it into the system? Is there a shield? How is it grounded?
Sorry that is all I can think of.
Regards
TK
Group: DynoMotion |
Message: 147 |
From: cees |
Date: 2/23/2010 |
Subject: Re: MPG problems |
I think the USB stuff is beyond the
knowledge, for the developers.
I am busy with the KFLOP and Kanalog now
for 4 months without pauses.
What I have seen, in this period.
Ghost, viruses, voodoo perhaps???
No!!
This USB is not for the real world.
A mice, or a printer, Yes okay, CNC with heavy
motors and heavy drives like a 4KW radar beam it is no good!!
It is not stable in a professionally CNC environment.
It sucks!!
Electrical noise, and a progam what is in a
kind of experimental stage.
We have to send Tom back to his developers
bench.
I am sorry, to have such a hard verdict.
But I am on the place where I started four months
ago, .. How do I control the beast.
Best Regards / M.vr.gr
Cees
C.J. Olgers
Lemmerkade 38 8244DC
Lelystad-Haven
Tel. : 0320-842939
Mobiel: 0624718690
K.v.K. Lelystad 34071687
b.t.w. nr. NL063838771B01
http://www.olgerstimmerwerk.nl
http://www.olgerstimmerwerk.nl/digitizer/Digitizer.htm
http://www.cncfrees.nl/
|
|
Group: DynoMotion |
Message: 148 |
From: babinda01 |
Date: 2/23/2010 |
Subject: Re: MPG problems |
Hi Cees,
I have been a CNC integrator of many years now, mainly on large machinery ie milling machines with 10+meters of travel in the X axis and 50 to 100Kw VFD Spindle drives. Noise is ALWAYS an issue - I have seen even the most hardened "Commercial Control" have issues in regard to noise.
Having said that, I have been installing a system using the Kflop & Kanalog for a while now too. I have had a few issues and a few problems, BUT Tom has always helped me out - most of these problems were my own lack of knowledge, some were features missing from the kflop/kanalog, but as I said Tom helped me out each time.
I too am unsure about USB and motion control, I have seen it fail (or not work properly) on two other recent USB based motion devices. I KNOW Windows is evil, evil, evil, terrible, terrible, terrible and shouldn't be used for motion control - and that is why we need devices like the kflop/kanalog.
Some thing COULD be done differently to enhance the system, but all this knowledge and after thought comes from other peoples experience using the device in different situations, there is no amount of testing on a bench that can make up for real world experience. If you want a good system for industrial use, the newer Fanuc controls are great, but they come at a price. So we all need to have a bit of give and take, and work together to get a system that works for the price we are willing to pay.
I have only this week got my machine running with the kflop/kanalog, and I will be testing it more intensly this week and next to see how it performs, and to see if I have any "Ghosts" hiding in my system. I am using AC servo motors and drives and have two VFD's controlling two spindles, I have all this crammed into one small electrical enclosure. The other day I was running some homing tests with rapid rates up around the 50 - 75 Meters/Minute and I homed to within about .01mm each time, so I have no issues with the accuracy of the system.
I feel you are being a little to harsh on Tom, he has been helpful to me.
I don't mean this post to be a bash up Cees post, so please don't take it that way. I can understand your frustration and I share your concerns about USB. But I do feel that you will get your system working with Toms help.
Regards
Andrew Erwood
AKSYS Tech Pty Ltd
Australia
andrew@...
--- In DynoMotion@yahoogroups.com, "cees" <c.olgers@...> wrote:
>
> I think the USB stuff is beyond the knowledge, for the developers.
>
> I am busy with the KFLOP and Kanalog now for 4 months without pauses.
>
> What I have seen, in this period.
>
> Ghost, viruses, voodoo perhaps???
>
> No!!
>
> This USB is not for the real world.
>
> A mice, or a printer, Yes okay, CNC with heavy motors and heavy drives like
> a 4KW radar beam it is no good!!
>
> It is not stable in a professionally CNC environment.
>
> It sucks!!
>
> Electrical noise, and a progam what is in a kind of experimental stage.
>
> We have to send Tom back to his developers bench.
>
> I am sorry, to have such a hard verdict.
>
> But I am on the place where I started four months ago, .. How do I control
> the beast.
>
>
>
> Best Regards / M.vr.gr
>
> Cees
>
>
>
> C.J. Olgers
>
> Lemmerkade 38 8244DC
>
> Lelystad-Haven
>
> Tel. : 0320-842939
>
> Mobiel: 0624718690
>
> K.v.K. Lelystad 34071687
>
> b.t.w. nr. NL063838771B01
>
> <http://www.olgerstimmerwerk.nl/> http://www.olgerstimmerwerk.nl
>
> <http://www.olgerstimmerwerk.nl/digitizer/Digitizer.htm>
> http://www.olgerstimmerwerk.nl/digitizer/Digitizer.htm
>
> <http://www.cncfrees.nl/> http://www.cncfrees.nl/
>
|
|
Group: DynoMotion |
Message: 149 |
From: bigtoy302 |
Date: 2/23/2010 |
Subject: Re: MPG problems |
I have the MPG hooked up to jp6 just like the diagram said. I used a db25 mounted on my control box then it goes to the kflop. I did not modify the mpg harness at all. I used the db25 that was on it when I got it. I think I may be getting noise fed back into the x and y encoders. I do not have the shields hooked up them yet. I will hook them up and try it again. I have the kanalog mounted to the control cabinet using the hardware provided. I used the outside holes to mount the board not the ones marked ground.
Check out my build thread here for pictures of how I have everything mounted. http://www.cnczone.com/forums/showthread.php?t=94101
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Ryan,
>
> I have no idea why this is occurring. Could you provide more information? Such as when you say everything was working then failed, what was working? Jogging or GCode motion or sitting idle?Â
>
> Do you have the Keling wired up to the Aux1 connector?
>
> Possibilities I can think of might be:
>
> #1 - We don't have any protection against jogging on the MPG while GCode is running. To eliminate this as a possibility try re-assigning the A B Quadrature inputs to 46 and 47 (The KFlop LEDS) and see if a problem ever occurs (of course you wont be able to test jogging with the MPG).
>
> #2 - I just realized we are connecting 5V outputs to 3.3V inputs (with an internal 150 ohm pull down).  I doubt if this is a problem unless the MPG is driving the signals hard above 3.9V (because the 3.3V inputs are diode clamped to the 3.3V power rail).  Please check the outputs to see what voltage they rise to.  The ideal test would be disconnected from the KFlop and with a 150ohm pulldown resistor.  Or add 50 ohm series resistors to be safe.
>
> #3 - Possibly just the long MPG cable picking up noise and injecting it into the system? Is there a shield?  How is it grounded?
>
> Sorry that is all I can think of.
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: bigtoy302 <bigtoy302@...>
> To: DynoMotion@yahoogroups.com
> Sent: Mon, February 22, 2010 7:27:47 PM
> Subject: [DynoMotion] MPG problems
>
> Â
> I am in the process of getting my system all set up. I have a Kflop, snapamp, and kanalog together. I have everything tuned and I can jog everything just fine. So I installed my Keling MPG and everything was working good for a few minutes then all the sudden the x and y servos powered off the snapamp started twitching back and forth then would fault then spin out of control. If I unplug the mpg the motors work fine. As soon as I plug it back in the freak out again. If I unplug the snapamp I can still jog the Z ( powered from the kanalog just fine)with the mpg. I am running Mach also.
>
> Ryan
>
|
|
Group: DynoMotion |
Message: 152 |
From: cees |
Date: 2/24/2010 |
Subject: Re: MPG problems |
Hi Andrew
Ok, I am to harsh on Tom, he is very helpful to me also.
But I don’t know where to look anymore.
Yesterday it was again no joy, after a few weeks searching for “personality
modules for my old analog electro craft BRU 200 drives, without luck.
I came to the conclusion that these modules have some data
burned in for a motor what is attached at this drive, they have a battery what
hold fine tuning data for the P.I.D. parameters.
So they have basic information in them for the specific motor,
and then you can auto tune them with Hyperterminal .
This fine tuning can also be done in Kmotion, and then you can
store this data in a C-progam.
So there is no need to have the fine tuning P.I.D. data stored
in the personality module, ( after ten years these modules have to replaced
because the onboard battery has died)
But the basic parameters are still there.
So with this knowledge, I started with: a virus scan on my computer,
installed the service pack 2 usb driver because it is faster, I had installed
from the computer and all other gadgets and encoder 6mm² ground wires to a
big copper strip in the electrical cabinet to get a star shaped grounding, to
eliminate the electrical noise .
You have to know that all this was after I have got the machine
running in December, it did three axes and spindle. And I was happy as a child.
This was a beginning, because it has limit switches, a pneumatic
driven 8 tools changer on his arm on the Y axe, so I had more hair loss to go. I
want to start something simple, I tried the Xbox plug-in with a wireless Xbox
controller, with this plug-in the machine went nuts, and drive the 1500kg X axe
with the speed of light to my neighbor across the street.
I had uninstalled the plug-in, and now for some strange reason I
know the C-progam file was changed, the input gain for the X axe was changed
from -1 to plus 1, this looks like a minor case, but there is suddenly a 10
volt output on the analog drive and he is going on maximum speed to his grave.
Yesterday I made a new start, made a new tuning C-progam al from
the start.
After this it was running again. Now the next step, I putted in
the C-progam for the Limit switches to get them working.
I had them at first configurated in Mach3 but there was a
problem with the in and outputs above 128 for some reason, so with the help of
Tom I wrote the C-progam.
I must say, I don’t have any experience with this kind of programming,
I don’t understand this Kmotion software for more than 5%.
It is all new for me, I have build three stepper machines, and that’s
all, never heard about P.I.D. before and no experience with servo motors.
Then there is the Language, I am Dutch so the manuals are a kind
of Chinese for me.
After the lunch break I started the machine again, my wife was
there to look at my progress and to see it move again properly.
Now the Y axe went nuts and hit the end of his travel so hard,
that the end plate (15mm thick steel plate was bend) and the steel bearing
balls went ejected from the ball bearing nut.
Another change in the Init C-progam, again a gain what was
changed from 1 to -1.
So I did change it back, get rid of the home limit progam, to
get again in the state I was before, with no luck.
Now it is telling me all kind of fault messages, and I am not
able to get the three axes running like they did.
I don’t know anymore, and I am freightfull to start it
again.
Conclusion:
I don’t understand the Kmotion software enough.
The software and Kflop comes from a guy who is willing to give
all the help I need.
I am a sort of experimental object.
Mach3 has 9 years of history with now about 12000 users, with
all there specific needs and bugs they found out. Brian Barker is rewriting it
now, and he hopes to get it done at the end of this year.
So I know it is very complex.
I have no luck.
So my mail was not intended to burn Tom to the ground.
Regards,
Cees
Van:
DynoMotion@yahoogroups.com [mailto: DynoMotion@yahoogroups.com] Namens babinda01
Verzonden: dinsdag 23 februari 2010 23:00
Aan: DynoMotion@yahoogroups.com
Onderwerp: [DynoMotion] Re: MPG problems
Hi Cees,
I have been a CNC integrator of many years now, mainly on large machinery ie
milling machines with 10+meters of travel in the X axis and 50 to 100Kw VFD
Spindle drives. Noise is ALWAYS an issue - I have seen even the most hardened
"Commercial Control" have issues in regard to noise.
Having said that, I have been installing a system using the Kflop & Kanalog
for a while now too. I have had a few issues and a few problems, BUT Tom has
always helped me out - most of these problems were my own lack of knowledge,
some were features missing from the kflop/kanalog, but as I said Tom helped me
out each time.
I too am unsure about USB and motion control, I have seen it fail (or not work
properly) on two other recent USB based motion devices. I KNOW Windows is evil,
evil, evil, terrible, terrible, terrible and shouldn't be used for motion
control - and that is why we need devices like the kflop/kanalog.
Some thing COULD be done differently to enhance the system, but all this
knowledge and after thought comes from other peoples experience using the
device in different situations, there is no amount of testing on a bench that
can make up for real world experience. If you want a good system for industrial
use, the newer Fanuc controls are great, but they come at a price. So we all
need to have a bit of give and take, and work together to get a system that
works for the price we are willing to pay.
I have only this week got my machine running with the kflop/kanalog, and I will
be testing it more intensly this week and next to see how it performs, and to
see if I have any "Ghosts" hiding in my system. I am using AC servo
motors and drives and have two VFD's controlling two spindles, I have all this
crammed into one small electrical enclosure. The other day I was running some
homing tests with rapid rates up around the 50 - 75 Meters/Minute and I homed
to within about .01mm each time, so I have no issues with the accuracy of the
system.
I feel you are being a little to harsh on Tom, he has been helpful to me.
I don't mean this post to be a bash up Cees post, so please don't take it that
way. I can understand your frustration and I share your concerns about USB. But
I do feel that you will get your system working with Toms help.
Regards
Andrew Erwood
AKSYS Tech Pty Ltd
Australia
andrew@...
--- In DynoMotion@yahoogroups.com,
"cees" <c.olgers@...> wrote:
>
> I think the USB stuff is beyond the knowledge, for the developers.
>
> I am busy with the KFLOP and Kanalog now for 4 months without pauses.
>
> What I have seen, in this period.
>
> Ghost, viruses, voodoo perhaps???
>
> No!!
>
> This USB is not for the real world.
>
> A mice, or a printer, Yes okay, CNC with heavy motors and heavy drives
like
> a 4KW radar beam it is no good!!
>
> It is not stable in a professionally CNC environment.
>
> It sucks!!
>
> Electrical noise, and a progam what is in a kind of experimental stage.
>
> We have to send Tom back to his developers bench.
>
> I am sorry, to have such a hard verdict.
>
> But I am on the place where I started four months ago, .. How do I control
> the beast.
>
>
>
> Best Regards / M.vr.gr
>
> Cees
>
>
>
> C.J. Olgers
>
> Lemmerkade 38 8244DC
>
> Lelystad-Haven
>
> Tel. : 0320-842939
>
> Mobiel: 0624718690
>
> K.v.K. Lelystad 34071687
>
> b.t.w. nr. NL063838771B01
>
> <http://www.olgerstimmerwerk.nl/>
http://www.olgerstimmerwerk.nl
>
> <http://www.olgerstimmerwerk.nl/digitizer/Digitizer.htm>
> http://www.olgerstimmerwerk.nl/digitizer/Digitizer.htm
>
> <http://www.cncfrees.nl/> href="http://www.cncfrees.nl/">http://www.cncfrees.nl/
>
|
|
Group: DynoMotion |
Message: 153 |
From: babinda01 |
Date: 2/24/2010 |
Subject: Re: MPG problems |
Hi Cees,
WOW!!!!! I think I would be bald by now (from pulling my hair out).
Firstly in regard to the I/O bits above 128 - Tom has rewitten the Mach3 plug-in to handle these now - this was one of the issues I had problem with, that I mentioned in my last post.
I know mach3 has been around for quite some time and has quite a lot of happy users - BUT - it is not perfect, the current project I have been working on has been a long project which started nearly three year ago, when I was contracted to write some software to control these machines. The company who contracted me specified that Mach3 must be the CNC engine behind the software, and so I did as they asked, but it was a major task, I found major problems with the macropump and with scripting in general within mach, and in the end I ended up rewritting the macropump (now controlled by my program and not mach3) so that I could get it to work properly.
Firstly change all your velocities to a much lower level until you get your system sorted, this will stop it taking off like the devil and causing you more grief than you need. Once things are running well then ramp them up.
Try and use as few plugin as possible with mach - I don't know anything about the 360 plugin. But I would ditch it until you are happy with the machine in a basic state.
I know some of this you have/are trying - but if you can get things working in stages it may make life easier for you.
Regards
Andrew
--- In DynoMotion@yahoogroups.com, "cees" <c.olgers@...> wrote:
>
> Hi Andrew
>
>
>
> Ok, I am to harsh on Tom, he is very helpful to me also.
>
> But I don't know where to look anymore.
>
> Yesterday it was again no joy, after a few weeks searching for "personality
> modules for my old analog electro craft BRU 200 drives, without luck.
>
> I came to the conclusion that these modules have some data burned in for a
> motor what is attached at this drive, they have a battery what hold fine
> tuning data for the P.I.D. parameters.
>
> So they have basic information in them for the specific motor, and then you
> can auto tune them with Hyperterminal .
>
> This fine tuning can also be done in Kmotion, and then you can store this
> data in a C-progam.
>
> So there is no need to have the fine tuning P.I.D. data stored in the
> personality module, ( after ten years these modules have to replaced because
> the onboard battery has died)
>
> But the basic parameters are still there.
>
> So with this knowledge, I started with: a virus scan on my computer,
> installed the service pack 2 usb driver because it is faster, I had
> installed from the computer and all other gadgets and encoder 6mm² ground
> wires to a big copper strip in the electrical cabinet to get a star shaped
> grounding, to eliminate the electrical noise .
>
>
>
> You have to know that all this was after I have got the machine running in
> December, it did three axes and spindle. And I was happy as a child.
>
> This was a beginning, because it has limit switches, a pneumatic driven 8
> tools changer on his arm on the Y axe, so I had more hair loss to go. I want
> to start something simple, I tried the Xbox plug-in with a wireless Xbox
> controller, with this plug-in the machine went nuts, and drive the 1500kg X
> axe with the speed of light to my neighbor across the street.
>
> I had uninstalled the plug-in, and now for some strange reason I know the
> C-progam file was changed, the input gain for the X axe was changed from -1
> to plus 1, this looks like a minor case, but there is suddenly a 10 volt
> output on the analog drive and he is going on maximum speed to his grave.
>
>
>
> Yesterday I made a new start, made a new tuning C-progam al from the start.
>
> After this it was running again. Now the next step, I putted in the C-progam
> for the Limit switches to get them working.
>
> I had them at first configurated in Mach3 but there was a problem with the
> in and outputs above 128 for some reason, so with the help of Tom I wrote
> the C-progam.
>
> I must say, I don't have any experience with this kind of programming, I
> don't understand this Kmotion software for more than 5%.
>
> It is all new for me, I have build three stepper machines, and that's all,
> never heard about P.I.D. before and no experience with servo motors.
>
> Then there is the Language, I am Dutch so the manuals are a kind of Chinese
> for me.
>
>
>
> After the lunch break I started the machine again, my wife was there to look
> at my progress and to see it move again properly.
>
> Now the Y axe went nuts and hit the end of his travel so hard, that the end
> plate (15mm thick steel plate was bend) and the steel bearing balls went
> ejected from the ball bearing nut.
>
> Another change in the Init C-progam, again a gain what was changed from 1 to
> -1.
>
> So I did change it back, get rid of the home limit progam, to get again in
> the state I was before, with no luck.
>
> Now it is telling me all kind of fault messages, and I am not able to get
> the three axes running like they did.
>
> I don't know anymore, and I am freightfull to start it again.
>
>
>
> Conclusion:
>
>
>
> I don't understand the Kmotion software enough.
>
> The software and Kflop comes from a guy who is willing to give all the help
> I need.
>
> I am a sort of experimental object.
>
> Mach3 has 9 years of history with now about 12000 users, with all there
> specific needs and bugs they found out. Brian Barker is rewriting it now,
> and he hopes to get it done at the end of this year.
>
> So I know it is very complex.
>
> I have no luck.
>
>
>
> So my mail was not intended to burn Tom to the ground.
>
>
>
> Regards,
>
> Cees
>
>
>
>
>
>
>
> Van: DynoMotion@yahoogroups.com [mailto: DynoMotion@yahoogroups.com] Namens
> babinda01
> Verzonden: dinsdag 23 februari 2010 23:00
> Aan: DynoMotion@yahoogroups.com
> Onderwerp: [DynoMotion] Re: MPG problems
>
>
>
>
>
> Hi Cees,
> I have been a CNC integrator of many years now, mainly on large machinery ie
> milling machines with 10+meters of travel in the X axis and 50 to 100Kw VFD
> Spindle drives. Noise is ALWAYS an issue - I have seen even the most
> hardened "Commercial Control" have issues in regard to noise.
>
> Having said that, I have been installing a system using the Kflop & Kanalog
> for a while now too. I have had a few issues and a few problems, BUT Tom has
> always helped me out - most of these problems were my own lack of knowledge,
> some were features missing from the kflop/kanalog, but as I said Tom helped
> me out each time.
>
> I too am unsure about USB and motion control, I have seen it fail (or not
> work properly) on two other recent USB based motion devices. I KNOW Windows
> is evil, evil, evil, terrible, terrible, terrible and shouldn't be used for
> motion control - and that is why we need devices like the kflop/kanalog.
> Some thing COULD be done differently to enhance the system, but all this
> knowledge and after thought comes from other peoples experience using the
> device in different situations, there is no amount of testing on a bench
> that can make up for real world experience. If you want a good system for
> industrial use, the newer Fanuc controls are great, but they come at a
> price. So we all need to have a bit of give and take, and work together to
> get a system that works for the price we are willing to pay.
>
> I have only this week got my machine running with the kflop/kanalog, and I
> will be testing it more intensly this week and next to see how it performs,
> and to see if I have any "Ghosts" hiding in my system. I am using AC servo
> motors and drives and have two VFD's controlling two spindles, I have all
> this crammed into one small electrical enclosure. The other day I was
> running some homing tests with rapid rates up around the 50 - 75
> Meters/Minute and I homed to within about .01mm each time, so I have no
> issues with the accuracy of the system.
>
> I feel you are being a little to harsh on Tom, he has been helpful to me.
> I don't mean this post to be a bash up Cees post, so please don't take it
> that way. I can understand your frustration and I share your concerns about
> USB. But I do feel that you will get your system working with Toms help.
>
> Regards
> Andrew Erwood
> AKSYS Tech Pty Ltd
> Australia
> andrew@... <mailto:andrew%40aksystech.com>
>
> --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ,
> "cees" <c.olgers@> wrote:
> >
> > I think the USB stuff is beyond the knowledge, for the developers.
> >
> > I am busy with the KFLOP and Kanalog now for 4 months without pauses.
> >
> > What I have seen, in this period.
> >
> > Ghost, viruses, voodoo perhaps???
> >
> > No!!
> >
> > This USB is not for the real world.
> >
> > A mice, or a printer, Yes okay, CNC with heavy motors and heavy drives
> like
> > a 4KW radar beam it is no good!!
> >
> > It is not stable in a professionally CNC environment.
> >
> > It sucks!!
> >
> > Electrical noise, and a progam what is in a kind of experimental stage.
> >
> > We have to send Tom back to his developers bench.
> >
> > I am sorry, to have such a hard verdict.
> >
> > But I am on the place where I started four months ago, .. How do I control
> > the beast.
> >
> >
> >
> > Best Regards / M.vr.gr
> >
> > Cees
> >
> >
> >
> > C.J. Olgers
> >
> > Lemmerkade 38 8244DC
> >
> > Lelystad-Haven
> >
> > Tel. : 0320-842939
> >
> > Mobiel: 0624718690
> >
> > K.v.K. Lelystad 34071687
> >
> > b.t.w. nr. NL063838771B01
> >
> > <http://www.olgerstimmerwerk.nl/> http://www.olgerstimmerwerk.nl
> >
> > <http://www.olgerstimmerwerk.nl/digitizer/Digitizer.htm>
> > http://www.olgerstimmerwerk.nl/digitizer/Digitizer.htm
> >
> > <http://www.cncfrees.nl/> http://www.cncfrees.nl/
> >
>
|
|
Group: DynoMotion |
Message: 180 |
From: zeeschuim |
Date: 3/3/2010 |
Subject: Re: MPG problems |
Hi Andrew and Tom
I am back in the game, the machine is running again.
It was a stack of problems, started with the Xbox 360 plug-in; this one turned the machine in a mad man. Then there was the Idea, of the personality module, told to me from the man from the support desk of Rockwell Automation. And then I made a mistake with loading the wrong firmware into the Kflop, there are two directories DSP_kmotion and DSP_kflop they have both an .Out file. It was not clear for me which file I needed, so I did Recovery with DSP_Kmotion and new file with DSP_Kflop. Then I get these very strange messages in Mach3.
Now I have started from the beginning, and yes it is running as it was in December. The new plug-in works for the output from the spindle. The C progam what Tom wrote for me for the spindle did not work anymore, I started the spindle with the digital out screen from the Kanalog, and only the stop command was working in Mach3, very strange.
Now we can use the in and outputs from Mach3, can I use these also for the -- limit/home switches? I hope so because these DynoMotion C-programs give me the creeps with their non predictable output.
I had gave the machine very small following errors, for 20mm, but when it is going nuts, it is going nuts what so ever.
Regards,
Cees
--- In DynoMotion@yahoogroups.com, "babinda01" <a_k@...> wrote:
>
> Hi Cees,
>
> WOW!!!!! I think I would be bald by now (from pulling my hair out).
> Firstly in regard to the I/O bits above 128 - Tom has rewitten the Mach3 plug-in to handle these now - this was one of the issues I had problem with, that I mentioned in my last post.
>
> I know mach3 has been around for quite some time and has quite a lot of happy users - BUT - it is not perfect, the current project I have been working on has been a long project which started nearly three year ago, when I was contracted to write some software to control these machines. The company who contracted me specified that Mach3 must be the CNC engine behind the software, and so I did as they asked, but it was a major task, I found major problems with the macropump and with scripting in general within mach, and in the end I ended up rewritting the macropump (now controlled by my program and not mach3) so that I could get it to work properly.
>
> Firstly change all your velocities to a much lower level until you get your system sorted, this will stop it taking off like the devil and causing you more grief than you need. Once things are running well then ramp them up.
>
> Try and use as few plugin as possible with mach - I don't know anything about the 360 plugin. But I would ditch it until you are happy with the machine in a basic state.
>
> I know some of this you have/are trying - but if you can get things working in stages it may make life easier for you.
>
> Regards
> Andrew
>
>
> --- In DynoMotion@yahoogroups.com, "cees" <c.olgers@> wrote:
> >
> > Hi Andrew
> >
> >
> >
> > Ok, I am to harsh on Tom, he is very helpful to me also.
> >
> > But I don't know where to look anymore.
> >
> > Yesterday it was again no joy, after a few weeks searching for "personality
> > modules for my old analog electro craft BRU 200 drives, without luck.
> >
> > I came to the conclusion that these modules have some data burned in for a
> > motor what is attached at this drive, they have a battery what hold fine
> > tuning data for the P.I.D. parameters.
> >
> > So they have basic information in them for the specific motor, and then you
> > can auto tune them with Hyperterminal .
> >
> > This fine tuning can also be done in Kmotion, and then you can store this
> > data in a C-progam.
> >
> > So there is no need to have the fine tuning P.I.D. data stored in the
> > personality module, ( after ten years these modules have to replaced because
> > the onboard battery has died)
> >
> > But the basic parameters are still there.
> >
> > So with this knowledge, I started with: a virus scan on my computer,
> > installed the service pack 2 usb driver because it is faster, I had
> > installed from the computer and all other gadgets and encoder 6mm² ground
> > wires to a big copper strip in the electrical cabinet to get a star shaped
> > grounding, to eliminate the electrical noise .
> >
> >
> >
> > You have to know that all this was after I have got the machine running in
> > December, it did three axes and spindle. And I was happy as a child.
> >
> > This was a beginning, because it has limit switches, a pneumatic driven 8
> > tools changer on his arm on the Y axe, so I had more hair loss to go. I want
> > to start something simple, I tried the Xbox plug-in with a wireless Xbox
> > controller, with this plug-in the machine went nuts, and drive the 1500kg X
> > axe with the speed of light to my neighbor across the street.
> >
> > I had uninstalled the plug-in, and now for some strange reason I know the
> > C-progam file was changed, the input gain for the X axe was changed from -1
> > to plus 1, this looks like a minor case, but there is suddenly a 10 volt
> > output on the analog drive and he is going on maximum speed to his grave.
> >
> >
> >
> > Yesterday I made a new start, made a new tuning C-progam al from the start.
> >
> > After this it was running again. Now the next step, I putted in the C-progam
> > for the Limit switches to get them working.
> >
> > I had them at first configurated in Mach3 but there was a problem with the
> > in and outputs above 128 for some reason, so with the help of Tom I wrote
> > the C-progam.
> >
> > I must say, I don't have any experience with this kind of programming, I
> > don't understand this Kmotion software for more than 5%.
> >
> > It is all new for me, I have build three stepper machines, and that's all,
> > never heard about P.I.D. before and no experience with servo motors.
> >
> > Then there is the Language, I am Dutch so the manuals are a kind of Chinese
> > for me.
> >
> >
> >
> > After the lunch break I started the machine again, my wife was there to look
> > at my progress and to see it move again properly.
> >
> > Now the Y axe went nuts and hit the end of his travel so hard, that the end
> > plate (15mm thick steel plate was bend) and the steel bearing balls went
> > ejected from the ball bearing nut.
> >
> > Another change in the Init C-progam, again a gain what was changed from 1 to
> > -1.
> >
> > So I did change it back, get rid of the home limit progam, to get again in
> > the state I was before, with no luck.
> >
> > Now it is telling me all kind of fault messages, and I am not able to get
> > the three axes running like they did.
> >
> > I don't know anymore, and I am freightfull to start it again.
> >
> >
> >
> > Conclusion:
> >
> >
> >
> > I don't understand the Kmotion software enough.
> >
> > The software and Kflop comes from a guy who is willing to give all the help
> > I need.
> >
> > I am a sort of experimental object.
> >
> > Mach3 has 9 years of history with now about 12000 users, with all there
> > specific needs and bugs they found out. Brian Barker is rewriting it now,
> > and he hopes to get it done at the end of this year.
> >
> > So I know it is very complex.
> >
> > I have no luck.
> >
> >
> >
> > So my mail was not intended to burn Tom to the ground.
> >
> >
> >
> > Regards,
> >
> > Cees
> >
> >
> >
> >
> >
> >
> >
> > Van: DynoMotion@yahoogroups.com [mailto: DynoMotion@yahoogroups.com] Namens
> > babinda01
> > Verzonden: dinsdag 23 februari 2010 23:00
> > Aan: DynoMotion@yahoogroups.com
> > Onderwerp: [DynoMotion] Re: MPG problems
> >
> >
> >
> >
> >
> > Hi Cees,
> > I have been a CNC integrator of many years now, mainly on large machinery ie
> > milling machines with 10+meters of travel in the X axis and 50 to 100Kw VFD
> > Spindle drives. Noise is ALWAYS an issue - I have seen even the most
> > hardened "Commercial Control" have issues in regard to noise.
> >
> > Having said that, I have been installing a system using the Kflop & Kanalog
> > for a while now too. I have had a few issues and a few problems, BUT Tom has
> > always helped me out - most of these problems were my own lack of knowledge,
> > some were features missing from the kflop/kanalog, but as I said Tom helped
> > me out each time.
> >
> > I too am unsure about USB and motion control, I have seen it fail (or not
> > work properly) on two other recent USB based motion devices. I KNOW Windows
> > is evil, evil, evil, terrible, terrible, terrible and shouldn't be used for
> > motion control - and that is why we need devices like the kflop/kanalog.
> > Some thing COULD be done differently to enhance the system, but all this
> > knowledge and after thought comes from other peoples experience using the
> > device in different situations, there is no amount of testing on a bench
> > that can make up for real world experience. If you want a good system for
> > industrial use, the newer Fanuc controls are great, but they come at a
> > price. So we all need to have a bit of give and take, and work together to
> > get a system that works for the price we are willing to pay.
> >
> > I have only this week got my machine running with the kflop/kanalog, and I
> > will be testing it more intensly this week and next to see how it performs,
> > and to see if I have any "Ghosts" hiding in my system. I am using AC servo
> > motors and drives and have two VFD's controlling two spindles, I have all
> > this crammed into one small electrical enclosure. The other day I was
> > running some homing tests with rapid rates up around the 50 - 75
> > Meters/Minute and I homed to within about .01mm each time, so I have no
> > issues with the accuracy of the system.
> >
> > I feel you are being a little to harsh on Tom, he has been helpful to me.
> > I don't mean this post to be a bash up Cees post, so please don't take it
> > that way. I can understand your frustration and I share your concerns about
> > USB. But I do feel that you will get your system working with Toms help.
> >
> > Regards
> > Andrew Erwood
> > AKSYS Tech Pty Ltd
> > Australia
> > andrew@ <mailto:andrew%40aksystech.com>
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ,
> > "cees" <c.olgers@> wrote:
> > >
> > > I think the USB stuff is beyond the knowledge, for the developers.
> > >
> > > I am busy with the KFLOP and Kanalog now for 4 months without pauses.
> > >
> > > What I have seen, in this period.
> > >
> > > Ghost, viruses, voodoo perhaps???
> > >
> > > No!!
> > >
> > > This USB is not for the real world.
> > >
> > > A mice, or a printer, Yes okay, CNC with heavy motors and heavy drives
> > like
> > > a 4KW radar beam it is no good!!
> > >
> > > It is not stable in a professionally CNC environment.
> > >
> > > It sucks!!
> > >
> > > Electrical noise, and a progam what is in a kind of experimental stage.
> > >
> > > We have to send Tom back to his developers bench.
> > >
> > > I am sorry, to have such a hard verdict.
> > >
> > > But I am on the place where I started four months ago, .. How do I control
> > > the beast.
> > >
> > >
> > >
> > > Best Regards / M.vr.gr
> > >
> > > Cees
> > >
> > >
> > >
> > > C.J. Olgers
> > >
> > > Lemmerkade 38 8244DC
> > >
> > > Lelystad-Haven
> > >
> > > Tel. : 0320-842939
> > >
> > > Mobiel: 0624718690
> > >
> > > K.v.K. Lelystad 34071687
> > >
> > > b.t.w. nr. NL063838771B01
> > >
> > > <http://www.olgerstimmerwerk.nl/> http://www.olgerstimmerwerk.nl
> > >
> > > <http://www.olgerstimmerwerk.nl/digitizer/Digitizer.htm>
> > > http://www.olgerstimmerwerk.nl/digitizer/Digitizer.htm
> > >
> > > <http://www.cncfrees.nl/> http://www.cncfrees.nl/
> > >
> >
>
|
|
Group: DynoMotion |
Message: 182 |
From: Tom Kerekes |
Date: 3/3/2010 |
Subject: Re: MPG problems |
Hi Cees,
We should probably attack the "going nuts" problem first. Can you be more specific? Can you offer any clues to when it happens and what you are doing? If you have the following error set for 20mm then if an axis takes off without being commanded to take off it should disable the axis and the DAC output should go to zero. Do you observe this after it happens? Check the status screens. Is the axis disabled? What do the DAC settings say? What is the minimum that you need to do to recover?
Regards
TK
Group: DynoMotion |
Message: 184 |
From: cees |
Date: 3/4/2010 |
Subject: Re: MPG problems |
Hi Tom
It is not something I like to reproduce, I know when it happens
with an Axe the “Inputgain0=” is changed from -1 to 1 or 1to-1, then the DAC
output for that axe is something like 9.777 volt with his destructive behavior.
Now I know where to look, change the “Inputgain0=” and then it
is ok again.
This has happen when I change a file in the configuration page
for the dynomotion plugin, I make the change, go jogging with one axe on my
Shuttlepro, and then it was going nuts.
Regards,
Cees
Van:
DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] Namens Tom
Kerekes
Verzonden: donderdag 4 maart 2010 8:22
Aan: DynoMotion@yahoogroups.com
Onderwerp: Re: [DynoMotion] Re: MPG problems
We
should probably attack the "going nuts" problem first. Can you
be more specific? Can you offer any clues to when it happens and what you
are doing? If you have the following error set for 20mm then if an
axis takes off without being commanded to take off it should disable the axis
and the DAC output should go to zero. Do you observe this after it
happens? Check the status screens. Is the axis disabled? What
do the DAC settings say? What is the minimum that you need to do to
recover?
From: zeeschuim
<c.olgers@...>
To: DynoMotion@yahoogroups.com
Sent: Wed, March 3, 2010 9:03:09 AM
Subject: [DynoMotion] Re: MPG problems
Hi Andrew and Tom
I am back in the game, the machine is running again.
It was a stack of problems, started with the Xbox 360 plug-in; this one turned
the machine in a mad man. Then there was the Idea, of the personality module,
told to me from the man from the support desk of Rockwell Automation. And then
I made a mistake with loading the wrong firmware into the Kflop, there are two
directories DSP_kmotion and DSP_kflop they have both an .Out file. It was not
clear for me which file I needed, so I did Recovery with DSP_Kmotion and new
file with DSP_Kflop. Then I get these very strange messages in Mach3.
Now I have started from the beginning, and yes it is running as it was in
December. The new plug-in works for the output from the spindle. The C progam
what Tom wrote for me for the spindle did not work anymore, I started the
spindle with the digital out screen from the Kanalog, and only the stop command
was working in Mach3, very strange.
Now we can use the in and outputs from Mach3, can I use these also for the --
limit/home switches? I hope so because these DynoMotion C-programs give me the
creeps with their non predictable output.
I had gave the machine very small following errors, for 20mm, but when it is
going nuts, it is going nuts what so ever.
Regards,
Cees
--- In DynoMotion@yahoogro
ups.com, "babinda01" <a_k@...> wrote:
>
> Hi Cees,
>
> WOW!!!!! I think I would be bald by now (from pulling my hair out).
> Firstly in regard to the I/O bits above 128 - Tom has rewitten the Mach3
plug-in to handle these now - this was one of the issues I had problem with,
that I mentioned in my last post.
>
> I know mach3 has been around for quite some time and has quite a lot of
happy users - BUT - it is not perfect, the current project I have been working
on has been a long project which started nearly three year ago, when I was
contracted to write some software to control these machines. The company who
contracted me specified that Mach3 must be the CNC engine behind the software,
and so I did as they asked, but it was a major task, I found major problems
with the macropump and with scripting in general within mach, and in the end I
ended up rewritting the macropump (now controlled by my program and not mach3)
so that I could get it to work properly.
>
> Firstly change all your velocities to a much lower level until you get
your system sorted, this will stop it taking off like the devil and causing you
more grief than you need. Once things are running well then ramp them up.
>
> Try and use as few plugin as possible with mach - I don't know anything
about the 360 plugin. But I would ditch it until you are happy with the machine
in a basic state.
>
> I know some of this you have/are trying - but if you can get things
working in stages it may make life easier for you.
>
> Regards
> Andrew
>
>
> --- In DynoMotion@yahoogro
ups.com, "cees" <c.olgers@> wrote:
> >
> > Hi Andrew
> >
> >
> >
> > Ok, I am to harsh on Tom, he is very helpful to me also.
> >
> > But I don't know where to look anymore.
> >
> > Yesterday it was again no joy, after a few weeks searching for
"personality
> > modules for my old analog electro craft BRU 200 drives, without luck.
> >
> > I came to the conclusion that these modules have some data burned in for
a
> > motor what is attached at this drive, they have a battery what hold
fine
> > tuning data for the P.I.D. parameters.
> >
> > So they have basic information in them for the specific motor, and
then you
> > can auto tune them with Hyperterminal .
> >
> > This fine tuning can also be done in Kmotion, and then you can store
this
> > data in a C-progam.
> >
> > So there is no need to have the fine tuning P.I.D. data stored in the
> > personality module, ( after ten years these modules have to replaced
because
> > the onboard battery has died)
> >
> > But the basic parameters are still there.
> >
> > So with this knowledge, I started with: a virus scan on my computer,
> > installed the service pack 2 usb driver because it is faster, I had
> > installed from the computer and all other gadgets and encoder 6mm²
ground
> > wires to a big copper strip in the electrical cabinet to get a star
shaped
> > grounding, to eliminate the electrical noise .
> >
> >
> >
> > You have to know that all this was after I have got the machine
running in
> > December, it did three axes and spindle. And I was happy as a child.
> >
> > This was a beginning, because it has limit switches, a pneumatic
driven 8
> > tools changer on his arm on the Y axe, so I had more hair loss to go.
I want
> > to start something simple, I tried the Xbox plug-in with a wireless
Xbox
> > controller, with this plug-in the machine went nuts, and drive the
1500kg X
> > axe with the speed of light to my neighbor across the street.
> >
> > I had uninstalled the plug-in, and now for some strange reason I know
the
> > C-progam file was changed, the input gain for the X axe was changed
from -1
> > to plus 1, this looks like a minor case, but there is suddenly a 10
volt
> > output on the analog drive and he is going on maximum speed to his
grave.
> >
> >
> >
> > Yesterday I made a new start, made a new tuning C-progam al from the
start.
> >
> > After this it was running again. Now the next step, I putted in the
C-progam
> > for the Limit switches to get them working.
> >
> > I had them at first configurated in Mach3 but there was a problem
with the
> > in and outputs above 128 for some reason, so with the help of Tom I
wrote
> > the C-progam.
> >
> > I must say, I don't have any experience with this kind of
programming, I
> > don't understand this Kmotion software for more than 5%.
> >
> > It is all new for me, I have build three stepper machines, and that's
all,
> > never heard about P.I.D. before and no experience with servo motors.
> >
> > Then there is the Language, I am Dutch so the manuals are a kind of
Chinese
> > for me.
> >
> >
> >
> > After the lunch break I started the machine again, my wife was there
to look
> > at my progress and to see it move again properly.
> >
> > Now the Y axe went nuts and hit the end of his travel so hard, that
the end
> > plate (15mm thick steel plate was bend) and the steel bearing balls
went
> > ejected from the ball bearing nut.
> >
> > Another change in the Init C-progam, again a gain what was changed from
1 to
> > -1.
> >
> > So I did change it back, get rid of the home limit progam, to get
again in
> > the state I was before, with no luck.
> >
> > Now it is telling me all kind of fault messages, and I am not able to
get
> > the three axes running like they did.
> >
> > I don't know anymore, and I am freightfull to start it again.
> >
> >
> >
> > Conclusion:
> >
> >
> >
> > I don't understand the Kmotion software enough.
> >
> > The software and Kflop comes from a guy who is willing to give all
the help
> > I need.
> >
> > I am a sort of experimental object.
> >
> > Mach3 has 9 years of history with now about 12000 users, with all
there
> > specific needs and bugs they found out. Brian Barker is rewriting it
now,
> > and he hopes to get it done at the end of this year.
> >
> > So I know it is very complex.
> >
> > I have no luck.
> >
> >
> >
> > So my mail was not intended to burn Tom to the ground.
> >
> >
> >
> > Regards,
> >
> > Cees
> >
> >
> >
> >
> >
> >
> >
> > Van: DynoMotion@yahoogro
ups.com [mailto: DynoMotion@yahoogro ups.com] Namens
> > babinda01
> > Verzonden: dinsdag 23 februari 2010 23:00
> > Aan: DynoMotion@yahoogro
ups.com
> > Onderwerp: [DynoMotion] Re: MPG problems
> >
> >
> >
> >
> >
> > Hi Cees,
> > I have been a CNC integrator of many years now, mainly on large
machinery ie
> > milling machines with 10+meters of travel in the X axis and 50 to
100Kw VFD
> > Spindle drives. Noise is ALWAYS an issue - I have seen even the most
> > hardened "Commercial Control" have issues in regard to
noise.
> >
> > Having said that, I have been installing a system using the Kflop
& Kanalog
> > for a while now too. I have had a few issues and a few problems, BUT
Tom has
> > always helped me out - most of these problems were my own lack of
knowledge,
> > some were features missing from the kflop/kanalog, but as I said Tom
helped
> > me out each time.
> >
> > I too am unsure about USB and motion control, I have seen it fail (or
not
> > work properly) on two other recent USB based motion devices. I KNOW
Windows
> > is evil, evil, evil, terrible, terrible, terrible and shouldn't be
used for
> > motion control - and that is why we need devices like the
kflop/kanalog.
> > Some thing COULD be done differently to enhance the system, but all
this
> > knowledge and after thought comes from other peoples experience using
the
> > device in different situations, there is no amount of testing on a
bench
> > that can make up for real world experience. If you want a good system
for
> > industrial use, the newer Fanuc controls are great, but they come at
a
> > price. So we all need to have a bit of give and take, and work
together to
> > get a system that works for the price we are willing to pay.
> >
> > I have only this week got my machine running with the kflop/kanalog,
and I
> > will be testing it more intensly this week and next to see how it
performs,
> > and to see if I have any "Ghosts" hiding in my system. I am
using AC servo
> > motors and drives and have two VFD's controlling two spindles, I have
all
> > this crammed into one small electrical enclosure. The other day I was
> > running some homing tests with rapid rates up around the 50 - 75
> > Meters/Minute and I homed to within about .01mm each time, so I have
no
> > issues with the accuracy of the system.
> >
> > I feel you are being a little to harsh on Tom, he has been helpful to
me.
> > I don't mean this post to be a bash up Cees post, so please don't
take it
> > that way. I can understand your frustration and I share your concerns
about
> > USB. But I do feel that you will get your system working with Toms
help.
> >
> > Regards
> > Andrew Erwood
> > AKSYS Tech Pty Ltd
> > Australia
> > andrew@ <mailto:andrew% 40aksystech. com>
> >
> > --- In DynoMotion@yahoogro
ups.com <mailto:DynoMotion% 40yahoogroups. com> ,
> > "cees" <c.olgers@> wrote:
> > >
> > > I think the USB stuff is beyond the knowledge, for the
developers.
> > >
> > > I am busy with the KFLOP and Kanalog now for 4 months without
pauses.
> > >
> > > What I have seen, in this period.
> > >
> > > Ghost, viruses, voodoo perhaps???
> > >
> > > No!!
> > >
> > > This USB is not for the real world.
> > >
> > > A mice, or a printer, Yes okay, CNC with heavy motors and heavy
drives
> > like
> > > a 4KW radar beam it is no good!!
> > >
> > > It is not stable in a professionally CNC environment.
> > >
> > > It sucks!!
> > >
> > > Electrical noise, and a progam what is in a kind of experimental
stage.
> > >
> > > We have to send Tom back to his developers bench.
> > >
> > > I am sorry, to have such a hard verdict.
> > >
> > > But I am on the place where I started four months ago, .. How do
I control
> > > the beast.
> > >
> > >
> > >
> > > Best Regards / M.vr.gr
> > >
> > > Cees
> > >
> > >
> > >
> > > C.J. Olgers
> > >
> > > Lemmerkade 38 8244DC
> > >
> > > Lelystad-Haven
> > >
> > > Tel. : 0320-842939
> > >
> > > Mobiel: 0624718690
> > >
> > > K.v.K. Lelystad 34071687
> > >
> > > b.t.w. nr. NL063838771B01
> > >
> > > <http://www.olgersti
mmerwerk. nl/> http://www.olgersti
mmerwerk. nl
> > >
> > > < href="http://www.olgerstimmerwerk.nl/digitizer/Digitizer.htm" target="_blank">http://www.olgersti
mmerwerk. nl/digitizer/ Digitizer. htm>
> > > target="_blank">http://www.olgersti mmerwerk. nl/digitizer/ Digitizer. htm
> > >
> > > <http://www.cncfrees.nl/> target="_blank">http://www.cncfrees .nl/
> > >
> >
>
|
|
Group: DynoMotion |
Message: 185 |
From: Tom Kerekes |
Date: 3/4/2010 |
Subject: Re: MPG problems |
Hi Cees,
Changing the sign of anything in the servo loop will cause the servo to have positive feedback instead of negative feedback. This will cause the motor to move ever increasingly faster away from the target destination rather than converge toward it. But his should immediately trip a following error, disable the axis, and set the DAC signal to zero. If the axis doesn't disable then the following error must not actually be set to a small value. I think you should intentionally introduce the wrong gain and verify the system indeed trips a following error and no damage results (in some safe manner where if it doesn't, no major damage results).
I can't imagine how the gain changes by itself. Where are you looking at the gain? In the Init C program? Or on the screen?
One common source of confusion is how the parameters work and how they are changed. There is a single set of parameters in the KFLOP board that are currently in use at any one time. There are basically 3 ways that these parameters may be changed:
#1 - Downloading the screen values using the KMotion.exe program (Download, Enable, Move, Step buttons all automatically download the parameters in the screens to the board)
#2 - Running a C Init program that sets parameters (Pushing RESET im Mach3 runs this program).
#3 - Entering Console commands
So it should be understood that the values in the KMotion Screens do not necessarily represent the values in use. If for some reason you wish to know which parameters are currently in use, you may UPLOAD the parameters from KFLOP into the screens.
The normal proceedure for configuration and tuning of KFLOP is to use the KMotion.exe program's screen settings and repeatedly download the parameters to the board and verify everything is configured and tuned properly. When you are finally satisfied and are sure that the parameters in the screens have been downloaded and match the parameters in KFLOP and are working correctly, then the Screen Parameters can be converted to a C program using the C Code -> Clip Board Button. If later, changes are made to screen values without updating the C Program values, then there is a good chance of confusion.
Another possibility is that you simply have multiple C programs with different settings that you are somehow mixing up.
I hope this helps.
TK
Group: DynoMotion |
Message: 197 |
From: bigtoy302 |
Date: 3/7/2010 |
Subject: Re: MPG problems |
So, played with it a little bit more and found out if I take out the mpg part of the c program I can have the mpg pluged in with no problems. But as soon as I plug the mpg in with the mpg c program loaded the x and y motors instantly get some crazy command to move then fault. I am only running the set currents for the snapamp program and thisone. Here is a copy of my c program. maybe something is wrong with my c program?
#include "KMotionDef.h"
#define QA 26 // define to which IO bits the AB signals are connected
#define QB 27
main()
{
int BitA,Change1=0,Change2=0, DiffX2;
int PosNoWrap, NewPos, Pos=0, wraps;
double Factor=0;
SetBit(152);
SetBit(157);
SetBit(158);
ch0->InputMode=ENCODER_MODE;
ch0->OutputMode=DC_SERVO_MODE;
ch0->Vel=100000.000000;
ch0->Accel=4000000.000000;
ch0->Jerk=4000000.000000;
ch0->P=10.000000;
ch0->I=0.000000;
ch0->D=6.000000;
ch0->FFAccel=0.000000;
ch0->FFVel=0.000000;
ch0->MaxI=100.000000;
ch0->MaxErr=100.000000;
ch0->MaxOutput=500.000000;
ch0->DeadBandGain=1.000000;
ch0->DeadBandRange=0.000000;
ch0->InputChan0=0;
ch0->InputChan1=0;
ch0->OutputChan0=8;
ch0->OutputChan1=1;
ch0->LimitSwitchOptions=0x8989001f;
ch0->InputGain0=1.000000;
ch0->InputGain1=1.000000;
ch0->InputOffset0=0.000000;
ch0->InputOffset1=0.000000;
ch0->invDistPerCycle=1.000000;
ch0->Lead=0.000000;
ch0->MaxFollowingError=100.000000;
ch0->StepperAmplitude=250.000000;
ch0->iir[0].B0=1.000000;
ch0->iir[0].B1=0.000000;
ch0->iir[0].B2=0.000000;
ch0->iir[0].A1=0.000000;
ch0->iir[0].A2=0.000000;
ch0->iir[1].B0=1.000000;
ch0->iir[1].B1=0.000000;
ch0->iir[1].B2=0.000000;
ch0->iir[1].A1=0.000000;
ch0->iir[1].A2=0.000000;
ch0->iir[2].B0=1.000000;
ch0->iir[2].B1=0.000000;
ch0->iir[2].B2=0.000000;
ch0->iir[2].A1=0.000000;
ch0->iir[2].A2=0.000000;
EnableAxis(0);
ch1->InputMode=ENCODER_MODE;
ch1->OutputMode=DC_SERVO_MODE;
ch1->Vel=100000.000000;
ch1->Accel=4000000.000000;
ch1->Jerk=4000000.000000;
ch1->P=10.000000;
ch1->I=0.000000;
ch1->D=6.000000;
ch1->FFAccel=0.000000;
ch1->FFVel=0.000000;
ch1->MaxI=100.000000;
ch1->MaxErr=100.000000;
ch1->MaxOutput=500.000000;
ch1->DeadBandGain=1.000000;
ch1->DeadBandRange=0.000000;
ch1->InputChan0=1;
ch1->InputChan1=2;
ch1->OutputChan0=9;
ch1->OutputChan1=3;
ch1->LimitSwitchOptions=0x8b8b001f;
ch1->InputGain0=1.000000;
ch1->InputGain1=1.000000;
ch1->InputOffset0=0.000000;
ch1->InputOffset1=0.000000;
ch1->invDistPerCycle=1.000000;
ch1->Lead=0.000000;
ch1->MaxFollowingError=100.000000;
ch1->StepperAmplitude=250.000000;
ch1->iir[0].B0=1.000000;
ch1->iir[0].B1=0.000000;
ch1->iir[0].B2=0.000000;
ch1->iir[0].A1=0.000000;
ch1->iir[0].A2=0.000000;
ch1->iir[1].B0=1.000000;
ch1->iir[1].B1=0.000000;
ch1->iir[1].B2=0.000000;
ch1->iir[1].A1=0.000000;
ch1->iir[1].A2=0.000000;
ch1->iir[2].B0=1.000000;
ch1->iir[2].B1=0.000000;
ch1->iir[2].B2=0.000000;
ch1->iir[2].A1=0.000000;
ch1->iir[2].A2=0.000000;
EnableAxis(1);
ch2->InputMode=ENCODER_MODE;
ch2->OutputMode=DAC_SERVO_MODE;
ch2->Vel=850.000000;
ch2->Accel=50000000.000000;
ch2->Jerk=50000000.000000;
ch2->P=225.000000;
ch2->I=0.000000;
ch2->D=225.000000;
ch2->FFAccel=0.000000;
ch2->FFVel=0.000000;
ch2->MaxI=100.000000;
ch2->MaxErr=100.000000;
ch2->MaxOutput=2047.000000;
ch2->DeadBandGain=1.000000;
ch2->DeadBandRange=0.000000;
ch2->InputChan0=2;
ch2->InputChan1=2;
ch2->OutputChan0=0;
ch2->OutputChan1=1;
ch2->LimitSwitchOptions=0x0;
ch2->InputGain0=-1.000000;
ch2->InputGain1=1.000000;
ch2->InputOffset0=0.000000;
ch2->InputOffset1=0.000000;
ch2->invDistPerCycle=1.000000;
ch2->Lead=0.000000;
ch2->MaxFollowingError=10000000.000000;
ch2->StepperAmplitude=250.000000;
ch2->iir[0].B0=1.000000;
ch2->iir[0].B1=0.000000;
ch2->iir[0].B2=0.000000;
ch2->iir[0].A1=0.000000;
ch2->iir[0].A2=0.000000;
ch2->iir[1].B0=1.000000;
ch2->iir[1].B1=0.000000;
ch2->iir[1].B2=0.000000;
ch2->iir[1].A1=0.000000;
ch2->iir[1].A2=0.000000;
ch2->iir[2].B0=1.000000;
ch2->iir[2].B1=0.000000;
ch2->iir[2].B2=0.000000;
ch2->iir[2].A1=0.000000;
ch2->iir[2].A2=0.000000;
EnableAxis(2);
DefineCoordSystem(0,1,2,-1);
for(;;)
{
WaitNextTimeSlice();
// convert quadrature to 2 bit binary
BitA = ReadBit(26);
PosNoWrap = (ReadBit(27) ^ BitA) | (BitA<<1);
// Diff between expected position based on average of two prev deltas
// and position with no wraps. (Keep as X2 to avoid division by 2)
DiffX2 = 2*(Pos-PosNoWrap) + (Change2+Change1);
// Calc quadrature wraparounds to bring Diff nearest zero
// offset by 128 wraps to avoid requiring floor()
wraps = ((DiffX2+1028)>>3)-128;
// factor in the quadrature wraparounds
NewPos = PosNoWrap + (wraps<<2);
Change2 = Change1;
Change1 = NewPos - Pos;
Pos = NewPos;
if (ReadBit(31)) // is X1 selected?
Factor = 1.0;
else if (ReadBit(32)) // is X100 selected?
Factor = 75.0;
else // must be X10 then
Factor = 10.0;
if (ReadBit(28)) // is x selected?
ch0->Dest += Change1 * Factor;
else if (ReadBit(29)) // is y selected?
ch1->Dest += Change1 * Factor;
else if (ReadBit(30)) // is z selected?
ch2->Dest += Change1 * Factor;
}
return 0;
}
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Ryan,
>
> I have no idea why this is occurring. Could you provide more information? Such as when you say everything was working then failed, what was working? Jogging or GCode motion or sitting idle?Â
>
> Do you have the Keling wired up to the Aux1 connector?
>
> Possibilities I can think of might be:
>
> #1 - We don't have any protection against jogging on the MPG while GCode is running. To eliminate this as a possibility try re-assigning the A B Quadrature inputs to 46 and 47 (The KFlop LEDS) and see if a problem ever occurs (of course you wont be able to test jogging with the MPG).
>
> #2 - I just realized we are connecting 5V outputs to 3.3V inputs (with an internal 150 ohm pull down).  I doubt if this is a problem unless the MPG is driving the signals hard above 3.9V (because the 3.3V inputs are diode clamped to the 3.3V power rail).  Please check the outputs to see what voltage they rise to.  The ideal test would be disconnected from the KFlop and with a 150ohm pulldown resistor.  Or add 50 ohm series resistors to be safe.
>
> #3 - Possibly just the long MPG cable picking up noise and injecting it into the system? Is there a shield?  How is it grounded?
>
> Sorry that is all I can think of.
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: bigtoy302 <bigtoy302@...>
> To: DynoMotion@yahoogroups.com
> Sent: Mon, February 22, 2010 7:27:47 PM
> Subject: [DynoMotion] MPG problems
>
> Â
> I am in the process of getting my system all set up. I have a Kflop, snapamp, and kanalog together. I have everything tuned and I can jog everything just fine. So I installed my Keling MPG and everything was working good for a few minutes then all the sudden the x and y servos powered off the snapamp started twitching back and forth then would fault then spin out of control. If I unplug the mpg the motors work fine. As soon as I plug it back in the freak out again. If I unplug the snapamp I can still jog the Z ( powered from the kanalog just fine)with the mpg. I am running Mach also.
>
> Ryan
>
|
|
Group: DynoMotion |
Message: 198 |
From: Tom Kerekes |
Date: 3/7/2010 |
Subject: Re: MPG problems |
I can't see anything specific wrong. You aren't plugging in the mpg with power on or with the program running are you? I didn't see that you answered my previous questions, but this is a big clue. Please change the program to change the destinations of 3 unused axis to see what happens. Try changing:
if (ReadBit(28) ) // is x selected? ch0->Dest += Change1 * Factor; else if (ReadBit(29) ) // is y selected? ch1->Dest += Change1 * Factor; else if (ReadBit(30) ) // is z selected? ch2->Dest += Change1 * Factor;
To:
if (ReadBit(28) ) // is x selected? ch5->Dest += Change1 * Factor; else if (ReadBit(29) ) // is y selected? ch6->Dest += Change1 * Factor; else if (ReadBit(30) ) // is z selected? ch7->Dest += Change1 * Factor;
Then operate the MPG while observing the Axis Screen and Destinations 5,6,7. Do the destinations then move as expected? If so, move the x,y,z motors using console commands and check if the Destinations 5,6, or 7 also somehow change.
Thanks
TK
Group: DynoMotion |
Message: 199 |
From: bigtoy302 |
Date: 3/7/2010 |
Subject: Re: MPG problems |
I am plugging the mpg in when the the kflop and snapamp are on. Gcode is not running. I do not think I tried plugging it in then turning the power on. This may be the problem? Power spike when plugging it in? I won't have time to mess with it till Tuesday.
To answer yout original questions:
1. G code not running just sitting Idle.
2. I do not even have to jog it before it starts messing up. I unhooked the 5v from the mpg with the same problem.
3. Un modified mpg cable plugging into a db25 connector in my control cabinet and then going to the kflop jp6. I do not think it is a noise issue because the the Z powered from the Kanalog do not mess up only the XY powered off the snapamp. The x trips first then the Y. Unplug the snapamp and I can use the mpg fine on the Z.
On a side not I can't figure how to get my x and Y to home in mach. I have separate home and limit switches hooked up to jp12 and I can see them working in the mach screen, So that part works. I do not know what c program to use for homing and what other settings I need to set. I already modified the REF buttons in Mach like the manual said.
Ryan
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> I can't see anything specific wrong. You aren't plugging in the mpg with power on or with the program running are you? I didn't see that you answered my previous questions, but this is a big clue. Please change the program to change the destinations of 3 unused axis to see what happens. Try changing:
>
> if (ReadBit(28) ) // is x selected?
> ch0->Dest += Change1 * Factor;
> else if (ReadBit(29) ) // is y selected?
> ch1->Dest += Change1 * Factor;
> else if (ReadBit(30) ) // is z selected?
> ch2->Dest += Change1 * Factor;
>
> To:
>
> if (ReadBit(28) ) // is x selected?
> ch5->Dest += Change1 * Factor;
> else if (ReadBit(29) ) // is y selected?
> ch6->Dest += Change1 * Factor;
> else if (ReadBit(30) ) // is z selected?
> ch7->Dest += Change1 * Factor;
>
> Then operate the MPG while observing the Axis Screen and Destinations 5,6,7. Do the destinations then move as expected? If so, move the x,y,z motors using console commands and check if the Destinations 5,6, or 7 also somehow change.
>
> Thanks
> TK
>
>
>
> ________________________________
> From: bigtoy302 <bigtoy302@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sun, March 7, 2010 8:52:30 AM
> Subject: [DynoMotion] Re: MPG problems
>
> Â
> So, played with it a little bit more and found out if I take out the mpg part of the c program I can have the mpg pluged in with no problems. But as soon as I plug the mpg in with the mpg c program loaded the x and y motors instantly get some crazy command to move then fault. I am only running the set currents for the snapamp program and thisone. Here is a copy of my c program. maybe something is wrong with my c program?
>
> #include "KMotionDef. h"
>
> #define QA 26 // define to which IO bits the AB signals are connected
> #define QB 27
>
> main()
> {
> int BitA,Change1= 0,Change2= 0, DiffX2;
> int PosNoWrap, NewPos, Pos=0, wraps;
> double Factor=0;
>
> SetBit(152);
> SetBit(157);
> SetBit(158);
>
> ch0->InputMode= ENCODER_MODE;
> ch0->OutputMode= DC_SERVO_ MODE;
> ch0->Vel=100000. 000000;
> ch0->Accel=4000000. 000000;
> ch0->Jerk=4000000. 000000;
> ch0->P=10.000000;
> ch0->I=0.000000;
> ch0->D=6.000000;
> ch0->FFAccel= 0.000000;
> ch0->FFVel=0. 000000;
> ch0->MaxI=100. 000000;
> ch0->MaxErr= 100.000000;
> ch0->MaxOutput= 500.000000;
> ch0->DeadBandGain= 1.000000;
> ch0->DeadBandRange= 0.000000;
> ch0->InputChan0= 0;
> ch0->InputChan1= 0;
> ch0->OutputChan0= 8;
> ch0->OutputChan1= 1;
> ch0->LimitSwitchOpt ions=0x8989001f;
> ch0->InputGain0= 1.000000;
> ch0->InputGain1= 1.000000;
> ch0->InputOffset0= 0.000000;
> ch0->InputOffset1= 0.000000;
> ch0->invDistPerCycl e=1.000000;
> ch0->Lead=0. 000000;
> ch0->MaxFollowingEr ror=100.000000;
> ch0->StepperAmplitu de=250.000000;
>
> ch0->iir[0]. B0=1.000000;
> ch0->iir[0]. B1=0.000000;
> ch0->iir[0]. B2=0.000000;
> ch0->iir[0]. A1=0.000000;
> ch0->iir[0]. A2=0.000000;
>
> ch0->iir[1]. B0=1.000000;
> ch0->iir[1]. B1=0.000000;
> ch0->iir[1]. B2=0.000000;
> ch0->iir[1]. A1=0.000000;
> ch0->iir[1]. A2=0.000000;
>
> ch0->iir[2]. B0=1.000000;
> ch0->iir[2]. B1=0.000000;
> ch0->iir[2]. B2=0.000000;
> ch0->iir[2]. A1=0.000000;
> ch0->iir[2]. A2=0.000000;
>
>
>
> EnableAxis(0) ;
>
> ch1->InputMode= ENCODER_MODE;
> ch1->OutputMode= DC_SERVO_ MODE;
> ch1->Vel=100000. 000000;
> ch1->Accel=4000000. 000000;
> ch1->Jerk=4000000. 000000;
> ch1->P=10.000000;
> ch1->I=0.000000;
> ch1->D=6.000000;
> ch1->FFAccel= 0.000000;
> ch1->FFVel=0. 000000;
> ch1->MaxI=100. 000000;
> ch1->MaxErr= 100.000000;
> ch1->MaxOutput= 500.000000;
> ch1->DeadBandGain= 1.000000;
> ch1->DeadBandRange= 0.000000;
> ch1->InputChan0= 1;
> ch1->InputChan1= 2;
> ch1->OutputChan0= 9;
> ch1->OutputChan1= 3;
> ch1->LimitSwitchOpt ions=0x8b8b001f;
> ch1->InputGain0= 1.000000;
> ch1->InputGain1= 1.000000;
> ch1->InputOffset0= 0.000000;
> ch1->InputOffset1= 0.000000;
> ch1->invDistPerCycl e=1.000000;
> ch1->Lead=0. 000000;
> ch1->MaxFollowingEr ror=100.000000;
> ch1->StepperAmplitu de=250.000000;
>
> ch1->iir[0]. B0=1.000000;
> ch1->iir[0]. B1=0.000000;
> ch1->iir[0]. B2=0.000000;
> ch1->iir[0]. A1=0.000000;
> ch1->iir[0]. A2=0.000000;
>
> ch1->iir[1]. B0=1.000000;
> ch1->iir[1]. B1=0.000000;
> ch1->iir[1]. B2=0.000000;
> ch1->iir[1]. A1=0.000000;
> ch1->iir[1]. A2=0.000000;
>
> ch1->iir[2]. B0=1.000000;
> ch1->iir[2]. B1=0.000000;
> ch1->iir[2]. B2=0.000000;
> ch1->iir[2]. A1=0.000000;
> ch1->iir[2]. A2=0.000000;
>
> EnableAxis(1) ;
>
> ch2->InputMode= ENCODER_MODE;
> ch2->OutputMode= DAC_SERVO_ MODE;
> ch2->Vel=850. 000000;
> ch2->Accel=50000000 .000000;
> ch2->Jerk=50000000. 000000;
> ch2->P=225.000000;
> ch2->I=0.000000;
> ch2->D=225.000000;
> ch2->FFAccel= 0.000000;
> ch2->FFVel=0. 000000;
> ch2->MaxI=100. 000000;
> ch2->MaxErr= 100.000000;
> ch2->MaxOutput= 2047.000000;
> ch2->DeadBandGain= 1.000000;
> ch2->DeadBandRange= 0.000000;
> ch2->InputChan0= 2;
> ch2->InputChan1= 2;
> ch2->OutputChan0= 0;
> ch2->OutputChan1= 1;
> ch2->LimitSwitchOpt ions=0x0;
> ch2->InputGain0= -1.000000;
> ch2->InputGain1= 1.000000;
> ch2->InputOffset0= 0.000000;
> ch2->InputOffset1= 0.000000;
> ch2->invDistPerCycl e=1.000000;
> ch2->Lead=0. 000000;
> ch2->MaxFollowingEr ror=10000000. 000000;
> ch2->StepperAmplitu de=250.000000;
>
> ch2->iir[0]. B0=1.000000;
> ch2->iir[0]. B1=0.000000;
> ch2->iir[0]. B2=0.000000;
> ch2->iir[0]. A1=0.000000;
> ch2->iir[0]. A2=0.000000;
>
> ch2->iir[1]. B0=1.000000;
> ch2->iir[1]. B1=0.000000;
> ch2->iir[1]. B2=0.000000;
> ch2->iir[1]. A1=0.000000;
> ch2->iir[1]. A2=0.000000;
>
> ch2->iir[2]. B0=1.000000;
> ch2->iir[2]. B1=0.000000;
> ch2->iir[2]. B2=0.000000;
> ch2->iir[2]. A1=0.000000;
> ch2->iir[2]. A2=0.000000;
>
> EnableAxis(2) ;
>
> DefineCoordSystem( 0,1,2,-1) ;
>
> for(;;)
> {
> WaitNextTimeSlice( );
>
> // convert quadrature to 2 bit binary
> BitA = ReadBit(26);
> PosNoWrap = (ReadBit(27) ^ BitA) | (BitA<<1);
>
> // Diff between expected position based on average of two prev deltas
> // and position with no wraps. (Keep as X2 to avoid division by 2)
>
> DiffX2 = 2*(Pos-PosNoWrap) + (Change2+Change1) ;
>
> // Calc quadrature wraparounds to bring Diff nearest zero
> // offset by 128 wraps to avoid requiring floor()
> wraps = ((DiffX2+1028) >>3)-128;
>
> // factor in the quadrature wraparounds
> NewPos = PosNoWrap + (wraps<<2);
>
> Change2 = Change1;
> Change1 = NewPos - Pos;
> Pos = NewPos;
>
> if (ReadBit(31) ) // is X1 selected?
> Factor = 1.0;
> else if (ReadBit(32) ) // is X100 selected?
> Factor = 75.0;
> else // must be X10 then
> Factor = 10.0;
>
> if (ReadBit(28) ) // is x selected?
> ch0->Dest += Change1 * Factor;
> else if (ReadBit(29) ) // is y selected?
> ch1->Dest += Change1 * Factor;
> else if (ReadBit(30) ) // is z selected?
> ch2->Dest += Change1 * Factor;
>
> }
> return 0;
> }
>
> --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> >
> > Ryan,
> >
> > I have no idea why this is occurring.ÃÂ Could you provide more information?ÃÂ Such as when you say everything was working then failed, what was working?ÃÂ Jogging or GCode motion or sitting idle?ÃÂ
> >
> > Do you have the Keling wired up to the Aux1 connector?
> >
> > Possibilities I can think of might be:
> >
> > #1 - We don't have any protection against jogging on the MPG while GCode is running.ÃÂ To eliminate this as a possibility try re-assigning the A B Quadrature inputs to 46 and 47 (The KFlop LEDS) and see if a problem ever occurs (of course you wont be able to test jogging with the MPG).
> >
> > #2 - I just realized we are connecting 5V outputs to 3.3V inputs (with an internalÃÂ 150 ohm pull down).ÃÂ ÃÂ I doubt if this is a problem unless the MPG is driving the signals hard above 3.9V (because the 3.3V inputs are diode clamped to the 3.3V power rail).ÃÂ ÃÂ Please check the outputs to see what voltage they rise to.ÃÂ ÃÂ The ideal test would be disconnected from the KFlop and with a 150ohm pulldown resistor.ÃÂ ÃÂ Or add 50 ohm series resistors to be safe.
> >
> > #3 - Possibly just the long MPG cable picking up noise and injecting it into the system?ÃÂ Is there a shield?ÃÂ ÃÂ How is it grounded?
> >
> > Sorry that is all I can think of.
> >
> > Regards
> > TK
> >
> >
> >
> >
> > ____________ _________ _________ __
> > From: bigtoy302 <bigtoy302@ ..>
> > To: DynoMotion@yahoogro ups.com
> > Sent: Mon, February 22, 2010 7:27:47 PM
> > Subject: [DynoMotion] MPG problems
> >
> > ÃÂ
> > I am in the process of getting my system all set up. I have a Kflop, snapamp, and kanalog together. I have everything tuned and I can jog everything just fine. So I installed my Keling MPG and everything was working good for a few minutes then all the sudden the x and y servos powered off the snapamp started twitching back and forth then would fault then spin out of control. If I unplug the mpg the motors work fine. As soon as I plug it back in the freak out again. If I unplug the snapamp I can still jog the Z ( powered from the kanalog just fine)with the mpg. I am running Mach also.
> >
> > Ryan
> >
>
|
|
Group: DynoMotion |
Message: 200 |
From: Tom Kerekes |
Date: 3/8/2010 |
Subject: Re: MPG problems |
Well, connecting the mpg with power on will most likely cause the signals to toggle in unpredictable ways. But I'm having a hard time understanding when the problem occurs. Like 10 seconds after plugging in the cable? Or immediately?
Disconnecting the +5V is somewhat of an invalid test. The signals will then probably float to invalid levels, and be highly susceptible to any noise.
Also I don't follow your logic with removing the SnapAmp to prove it isn't a noise issue. As the SnapAmp may be the source of the noise. That was the idea behind asking you to reassign the inputs to the LEDs to elliminate that as a possibility.
The MPG program uses some assumptions of limited acceleration to extend the count rate to ~100KHz even though the software is only looping at 5KHz. Basically the frequency is not expected to change instantaneously. If it does or changes erratically, then the algorithm can get confused and think it is moving when it is not. You can defeat this feature and avoid this issue (but limit your count rate to 5 KHz). Try changing
Change2 = Change1; Change1 = NewPos - Pos;
to
Change2 = 0; Change1 = 0;
Thanks
TK
Group: DynoMotion |
Message: 201 |
From: bigtoy302 |
Date: 3/8/2010 |
Subject: Re: MPG problems |
The problem occurs the instant I plug the mpg in. I do not even have to jog it. Like I said earlier I will try out those things you suggested tomorrow. What about the homing I asked about in my last post.?
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Well, connecting the mpg with power on will most likely cause the signals to toggle in unpredictable ways. But I'm having a hard time understanding when the problem occurs. Like 10 seconds after plugging in the cable? Or immediately?
>
> Disconnecting the +5V is somewhat of an invalid test. The signals will then probably float to invalid levels, and be highly susceptible to any noise.
>
> Also I don't follow your logic with removing the SnapAmp to prove it isn't a noise issue. As the SnapAmp may be the source of the noise. That was the idea behind asking you to reassign the inputs to the LEDs to elliminate that as a possibility.
>
> The MPG program uses some assumptions of limited acceleration to extend the count rate to ~100KHz even though the software is only looping at 5KHz. Basically the frequency is not expected to change instantaneously. If it does or changes erratically, then the algorithm can get confused and think it is moving when it is not. You can defeat this feature and avoid this issue (but limit your count rate to 5 KHz). Try changing
>
> Change2 = Change1;
> Change1 = NewPos - Pos;
>
> to
>
> Change2 = 0;
> Change1 = 0;
>
> Thanks
>
> TK
>
>
>
>
> ________________________________
> From: bigtoy302 <bigtoy302@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sun, March 7, 2010 6:34:02 PM
> Subject: [DynoMotion] Re: MPG problems
>
> Â
> I am plugging the mpg in when the the kflop and snapamp are on. Gcode is not running. I do not think I tried plugging it in then turning the power on. This may be the problem? Power spike when plugging it in? I won't have time to mess with it till Tuesday.
>
> To answer yout original questions:
>
> 1. G code not running just sitting Idle.
> 2. I do not even have to jog it before it starts messing up. I unhooked the 5v from the mpg with the same problem.
> 3. Un modified mpg cable plugging into a db25 connector in my control cabinet and then going to the kflop jp6. I do not think it is a noise issue because the the Z powered from the Kanalog do not mess up only the XY powered off the snapamp. The x trips first then the Y. Unplug the snapamp and I can use the mpg fine on the Z.
>
> On a side not I can't figure how to get my x and Y to home in mach. I have separate home and limit switches hooked up to jp12 and I can see them working in the mach screen, So that part works. I do not know what c program to use for homing and what other settings I need to set. I already modified the REF buttons in Mach like the manual said.
>
> Ryan
>
> --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> >
> > I can't see anything specific wrong.ÃÂ You aren't plugging in the mpg with power on or with the program running are you?ÃÂ I didn't see that you answered my previous questions, but this is a big clue.ÃÂ Please change the program to change the destinations of 3 unused axis to see what happens.ÃÂ Try changing:
> >
> > if (ReadBit(28) ) // is x selected?
> > ch0->Dest += Change1 * Factor;
> > else if (ReadBit(29) ) // is y selected?
> > ch1->Dest += Change1 * Factor;
> > else if (ReadBit(30) ) // is z selected?
> > ch2->Dest += Change1 * Factor;
> >
> > To:
> >
> > if (ReadBit(28) ) // is x selected?
> > ch5->Dest += Change1 * Factor;
> > else if (ReadBit(29) ) // is y selected?
> > ch6->Dest += Change1 * Factor;
> > else if (ReadBit(30) ) // is z selected?
> > ch7->Dest += Change1 * Factor;
> >
> > Then operate the MPG while observing the Axis Screen and Destinations 5,6,7.ÃÂ Do the destinations then move as expected?ÃÂ If so, move the x,y,z motors using console commands and check if the Destinations 5,6, or 7 also somehow change.
> >
> > Thanks
> > TK
> >
> >
> >
> > ____________ _________ _________ __
> > From: bigtoy302 <bigtoy302@ ..>
> > To: DynoMotion@yahoogro ups.com
> > Sent: Sun, March 7, 2010 8:52:30 AM
> > Subject: [DynoMotion] Re: MPG problems
> >
> > ÃÂ
> > So, played with it a little bit more and found out if I take out the mpg part of the c program I can have the mpg pluged in with no problems. But as soon as I plug the mpg in with the mpg c program loaded the x and y motors instantly get some crazy command to move then fault. I am only running the set currents for the snapamp program and thisone. Here is a copy of my c program. maybe something is wrong with my c program?
> >
> > #include "KMotionDef. h"
> >
> > #define QA 26 // define to which IO bits the AB signals are connected
> > #define QB 27
> >
> > main()
> > {
> > int BitA,Change1= 0,Change2= 0, DiffX2;
> > int PosNoWrap, NewPos, Pos=0, wraps;
> > double Factor=0;
> >
> > SetBit(152);
> > SetBit(157);
> > SetBit(158);
> >
> > ch0->InputMode= ENCODER_MODE;
> > ch0->OutputMode= DC_SERVO_ MODE;
> > ch0->Vel=100000. 000000;
> > ch0->Accel=4000000. 000000;
> > ch0->Jerk=4000000. 000000;
> > ch0->P=10.000000;
> > ch0->I=0.000000;
> > ch0->D=6.000000;
> > ch0->FFAccel= 0.000000;
> > ch0->FFVel=0. 000000;
> > ch0->MaxI=100. 000000;
> > ch0->MaxErr= 100.000000;
> > ch0->MaxOutput= 500.000000;
> > ch0->DeadBandGain= 1.000000;
> > ch0->DeadBandRange= 0.000000;
> > ch0->InputChan0= 0;
> > ch0->InputChan1= 0;
> > ch0->OutputChan0= 8;
> > ch0->OutputChan1= 1;
> > ch0->LimitSwitchOpt ions=0x8989001f;
> > ch0->InputGain0= 1.000000;
> > ch0->InputGain1= 1.000000;
> > ch0->InputOffset0= 0.000000;
> > ch0->InputOffset1= 0.000000;
> > ch0->invDistPerCycl e=1.000000;
> > ch0->Lead=0. 000000;
> > ch0->MaxFollowingEr ror=100.000000;
> > ch0->StepperAmplitu de=250.000000;
> >
> > ch0->iir[0]. B0=1.000000;
> > ch0->iir[0]. B1=0.000000;
> > ch0->iir[0]. B2=0.000000;
> > ch0->iir[0]. A1=0.000000;
> > ch0->iir[0]. A2=0.000000;
> >
> > ch0->iir[1]. B0=1.000000;
> > ch0->iir[1]. B1=0.000000;
> > ch0->iir[1]. B2=0.000000;
> > ch0->iir[1]. A1=0.000000;
> > ch0->iir[1]. A2=0.000000;
> >
> > ch0->iir[2]. B0=1.000000;
> > ch0->iir[2]. B1=0.000000;
> > ch0->iir[2]. B2=0.000000;
> > ch0->iir[2]. A1=0.000000;
> > ch0->iir[2]. A2=0.000000;
> >
> >
> >
> > EnableAxis(0) ;
> >
> > ch1->InputMode= ENCODER_MODE;
> > ch1->OutputMode= DC_SERVO_ MODE;
> > ch1->Vel=100000. 000000;
> > ch1->Accel=4000000. 000000;
> > ch1->Jerk=4000000. 000000;
> > ch1->P=10.000000;
> > ch1->I=0.000000;
> > ch1->D=6.000000;
> > ch1->FFAccel= 0.000000;
> > ch1->FFVel=0. 000000;
> > ch1->MaxI=100. 000000;
> > ch1->MaxErr= 100.000000;
> > ch1->MaxOutput= 500.000000;
> > ch1->DeadBandGain= 1.000000;
> > ch1->DeadBandRange= 0.000000;
> > ch1->InputChan0= 1;
> > ch1->InputChan1= 2;
> > ch1->OutputChan0= 9;
> > ch1->OutputChan1= 3;
> > ch1->LimitSwitchOpt ions=0x8b8b001f;
> > ch1->InputGain0= 1.000000;
> > ch1->InputGain1= 1.000000;
> > ch1->InputOffset0= 0.000000;
> > ch1->InputOffset1= 0.000000;
> > ch1->invDistPerCycl e=1.000000;
> > ch1->Lead=0. 000000;
> > ch1->MaxFollowingEr ror=100.000000;
> > ch1->StepperAmplitu de=250.000000;
> >
> > ch1->iir[0]. B0=1.000000;
> > ch1->iir[0]. B1=0.000000;
> > ch1->iir[0]. B2=0.000000;
> > ch1->iir[0]. A1=0.000000;
> > ch1->iir[0]. A2=0.000000;
> >
> > ch1->iir[1]. B0=1.000000;
> > ch1->iir[1]. B1=0.000000;
> > ch1->iir[1]. B2=0.000000;
> > ch1->iir[1]. A1=0.000000;
> > ch1->iir[1]. A2=0.000000;
> >
> > ch1->iir[2]. B0=1.000000;
> > ch1->iir[2]. B1=0.000000;
> > ch1->iir[2]. B2=0.000000;
> > ch1->iir[2]. A1=0.000000;
> > ch1->iir[2]. A2=0.000000;
> >
> > EnableAxis(1) ;
> >
> > ch2->InputMode= ENCODER_MODE;
> > ch2->OutputMode= DAC_SERVO_ MODE;
> > ch2->Vel=850. 000000;
> > ch2->Accel=50000000 .000000;
> > ch2->Jerk=50000000. 000000;
> > ch2->P=225.000000;
> > ch2->I=0.000000;
> > ch2->D=225.000000;
> > ch2->FFAccel= 0.000000;
> > ch2->FFVel=0. 000000;
> > ch2->MaxI=100. 000000;
> > ch2->MaxErr= 100.000000;
> > ch2->MaxOutput= 2047.000000;
> > ch2->DeadBandGain= 1.000000;
> > ch2->DeadBandRange= 0.000000;
> > ch2->InputChan0= 2;
> > ch2->InputChan1= 2;
> > ch2->OutputChan0= 0;
> > ch2->OutputChan1= 1;
> > ch2->LimitSwitchOpt ions=0x0;
> > ch2->InputGain0= -1.000000;
> > ch2->InputGain1= 1.000000;
> > ch2->InputOffset0= 0.000000;
> > ch2->InputOffset1= 0.000000;
> > ch2->invDistPerCycl e=1.000000;
> > ch2->Lead=0. 000000;
> > ch2->MaxFollowingEr ror=10000000. 000000;
> > ch2->StepperAmplitu de=250.000000;
> >
> > ch2->iir[0]. B0=1.000000;
> > ch2->iir[0]. B1=0.000000;
> > ch2->iir[0]. B2=0.000000;
> > ch2->iir[0]. A1=0.000000;
> > ch2->iir[0]. A2=0.000000;
> >
> > ch2->iir[1]. B0=1.000000;
> > ch2->iir[1]. B1=0.000000;
> > ch2->iir[1]. B2=0.000000;
> > ch2->iir[1]. A1=0.000000;
> > ch2->iir[1]. A2=0.000000;
> >
> > ch2->iir[2]. B0=1.000000;
> > ch2->iir[2]. B1=0.000000;
> > ch2->iir[2]. B2=0.000000;
> > ch2->iir[2]. A1=0.000000;
> > ch2->iir[2]. A2=0.000000;
> >
> > EnableAxis(2) ;
> >
> > DefineCoordSystem( 0,1,2,-1) ;
> >
> > for(;;)
> > {
> > WaitNextTimeSlice( );
> >
> > // convert quadrature to 2 bit binary
> > BitA = ReadBit(26);
> > PosNoWrap = (ReadBit(27) ^ BitA) | (BitA<<1);
> >
> > // Diff between expected position based on average of two prev deltas
> > // and position with no wraps. (Keep as X2 to avoid division by 2)
> >
> > DiffX2 = 2*(Pos-PosNoWrap) + (Change2+Change1) ;
> >
> > // Calc quadrature wraparounds to bring Diff nearest zero
> > // offset by 128 wraps to avoid requiring floor()
> > wraps = ((DiffX2+1028) >>3)-128;
> >
> > // factor in the quadrature wraparounds
> > NewPos = PosNoWrap + (wraps<<2);
> >
> > Change2 = Change1;
> > Change1 = NewPos - Pos;
> > Pos = NewPos;
> >
> > if (ReadBit(31) ) // is X1 selected?
> > Factor = 1.0;
> > else if (ReadBit(32) ) // is X100 selected?
> > Factor = 75.0;
> > else // must be X10 then
> > Factor = 10.0;
> >
> > if (ReadBit(28) ) // is x selected?
> > ch0->Dest += Change1 * Factor;
> > else if (ReadBit(29) ) // is y selected?
> > ch1->Dest += Change1 * Factor;
> > else if (ReadBit(30) ) // is z selected?
> > ch2->Dest += Change1 * Factor;
> >
> > }
> > return 0;
> > }
> >
> > --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Ryan,
> > >
> > > I have no idea why this is occurring.ÃâàCould you provide more information?ÃâàSuch as when you say everything was working then failed, what was working?ÃâàJogging or GCode motion or sitting idle?ÃâÃÂ
> > >
> > > Do you have the Keling wired up to the Aux1 connector?
> > >
> > > Possibilities I can think of might be:
> > >
> > > #1 - We don't have any protection against jogging on the MPG while GCode is running.ÃâàTo eliminate this as a possibility try re-assigning the A B Quadrature inputs to 46 and 47 (The KFlop LEDS) and see if a problem ever occurs (of course you wont be able to test jogging with the MPG).
> > >
> > > #2 - I just realized we are connecting 5V outputs to 3.3V inputs (with an internalÃâà150 ohm pull down).ÃâàÃâàI doubt if this is a problem unless the MPG is driving the signals hard above 3.9V (because the 3.3V inputs are diode clamped to the 3.3V power rail).ÃâàÃâàPlease check the outputs to see what voltage they rise to.ÃâàÃâàThe ideal test would be disconnected from the KFlop and with a 150ohm pulldown resistor.ÃâàÃâàOr add 50 ohm series resistors to be safe.
> > >
> > > #3 - Possibly just the long MPG cable picking up noise and injecting it into the system?ÃâàIs there a shield?ÃâàÃâàHow is it grounded?
> > >
> > > Sorry that is all I can think of.
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > > ____________ _________ _________ __
> > > From: bigtoy302 <bigtoy302@ ..>
> > > To: DynoMotion@yahoogro ups.com
> > > Sent: Mon, February 22, 2010 7:27:47 PM
> > > Subject: [DynoMotion] MPG problems
> > >
> > > ÃâÃÂ
> > > I am in the process of getting my system all set up. I have a Kflop, snapamp, and kanalog together. I have everything tuned and I can jog everything just fine. So I installed my Keling MPG and everything was working good for a few minutes then all the sudden the x and y servos powered off the snapamp started twitching back and forth then would fault then spin out of control. If I unplug the mpg the motors work fine. As soon as I plug it back in the freak out again. If I unplug the snapamp I can still jog the Z ( powered from the kanalog just fine)with the mpg. I am running Mach also.
> > >
> > > Ryan
> > >
> >
>
|
|
Group: DynoMotion |
Message: 202 |
From: Tom Kerekes |
Date: 3/8/2010 |
Subject: Re: MPG problems |
Ryan,
Regarding Homing:
Test your homing by writing a simple program such as:
#include "KMotionDef.h"
#define Z 2
main()
{
DisableAxis(Z);
Zero(Z);
EnableAxisDest(Z,0.0);
Jog(Z,10000); // start moving
while (ReadBit(15)) ; // wait for switch (input #15) to change
Jog(Z,0); // StopMotion
while(!CheckDone(Z)) ;
Jog(Z,-3000); // start moving
while (!ReadBit(15)) ; // wait for switch (input #15) to change
MoveRelAtVel(Z,-900,3000); // Move a bit further down
while(!CheckDone(Z)) ;
Delay_sec(.25);
DisableAxis(Z);
Zero(Z);
EnableAxisDest(Z,0.0);
}
for each axis.
Note the program as written
#1 is for the Z axis which is defined as axis 2
#2 moves at velocity +10000 counts/sec to the switch which is connected to IO bit 15
#3 bit15 is wired to go low when hit
#4 then backs out of the switch at -3000 counts/sec until IO bit 15 returns high
#5 then continues another -900 counts inside the travel at a speed of 3000 counts/sec
#6 then zeros the destination at that position
You will need to modify it for your desired directions, speeds, polarities and such.
After it is working, merge the relevant code into the HomeMach3.c program.
Thanks
TK
Group: DynoMotion |
Message: 212 |
From: bigtoy302 |
Date: 3/11/2010 |
Subject: Re: MPG problems |
I changed the I changed the destinations to 5,6,7, and observed the same thing. I move the mpg one click(x1) and it moves the one click then states making more commands to move then faults. I left the snap amp on and the motors unplugged and it counts go up and down like they should using the mpg. As soon as try to jog it after I plugged the motors back in then restarted the system they go nuts again once I try to jog them. I a now thinking it is noise in between the snapamp and the motors. How am I supposed to ground the motors? How is the kflop and snapamp supposed to be grounded?
Ryan
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Well, connecting the mpg with power on will most likely cause the signals to toggle in unpredictable ways. But I'm having a hard time understanding when the problem occurs. Like 10 seconds after plugging in the cable? Or immediately?
>
> Disconnecting the +5V is somewhat of an invalid test. The signals will then probably float to invalid levels, and be highly susceptible to any noise.
>
> Also I don't follow your logic with removing the SnapAmp to prove it isn't a noise issue. As the SnapAmp may be the source of the noise. That was the idea behind asking you to reassign the inputs to the LEDs to elliminate that as a possibility.
>
> The MPG program uses some assumptions of limited acceleration to extend the count rate to ~100KHz even though the software is only looping at 5KHz. Basically the frequency is not expected to change instantaneously. If it does or changes erratically, then the algorithm can get confused and think it is moving when it is not. You can defeat this feature and avoid this issue (but limit your count rate to 5 KHz). Try changing
>
> Change2 = Change1;
> Change1 = NewPos - Pos;
>
> to
>
> Change2 = 0;
> Change1 = 0;
>
> Thanks
>
> TK
>
>
>
>
> ________________________________
> From: bigtoy302 <bigtoy302@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sun, March 7, 2010 6:34:02 PM
> Subject: [DynoMotion] Re: MPG problems
>
> Â
> I am plugging the mpg in when the the kflop and snapamp are on. Gcode is not running. I do not think I tried plugging it in then turning the power on. This may be the problem? Power spike when plugging it in? I won't have time to mess with it till Tuesday.
>
> To answer yout original questions:
>
> 1. G code not running just sitting Idle.
> 2. I do not even have to jog it before it starts messing up. I unhooked the 5v from the mpg with the same problem.
> 3. Un modified mpg cable plugging into a db25 connector in my control cabinet and then going to the kflop jp6. I do not think it is a noise issue because the the Z powered from the Kanalog do not mess up only the XY powered off the snapamp. The x trips first then the Y. Unplug the snapamp and I can use the mpg fine on the Z.
>
> On a side not I can't figure how to get my x and Y to home in mach. I have separate home and limit switches hooked up to jp12 and I can see them working in the mach screen, So that part works. I do not know what c program to use for homing and what other settings I need to set. I already modified the REF buttons in Mach like the manual said.
>
> Ryan
>
> --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> >
> > I can't see anything specific wrong.ÃÂ You aren't plugging in the mpg with power on or with the program running are you?ÃÂ I didn't see that you answered my previous questions, but this is a big clue.ÃÂ Please change the program to change the destinations of 3 unused axis to see what happens.ÃÂ Try changing:
> >
> > if (ReadBit(28) ) // is x selected?
> > ch0->Dest += Change1 * Factor;
> > else if (ReadBit(29) ) // is y selected?
> > ch1->Dest += Change1 * Factor;
> > else if (ReadBit(30) ) // is z selected?
> > ch2->Dest += Change1 * Factor;
> >
> > To:
> >
> > if (ReadBit(28) ) // is x selected?
> > ch5->Dest += Change1 * Factor;
> > else if (ReadBit(29) ) // is y selected?
> > ch6->Dest += Change1 * Factor;
> > else if (ReadBit(30) ) // is z selected?
> > ch7->Dest += Change1 * Factor;
> >
> > Then operate the MPG while observing the Axis Screen and Destinations 5,6,7.ÃÂ Do the destinations then move as expected?ÃÂ If so, move the x,y,z motors using console commands and check if the Destinations 5,6, or 7 also somehow change.
> >
> > Thanks
> > TK
> >
> >
> >
> > ____________ _________ _________ __
> > From: bigtoy302 <bigtoy302@ ..>
> > To: DynoMotion@yahoogro ups.com
> > Sent: Sun, March 7, 2010 8:52:30 AM
> > Subject: [DynoMotion] Re: MPG problems
> >
> > ÃÂ
> > So, played with it a little bit more and found out if I take out the mpg part of the c program I can have the mpg pluged in with no problems. But as soon as I plug the mpg in with the mpg c program loaded the x and y motors instantly get some crazy command to move then fault. I am only running the set currents for the snapamp program and thisone. Here is a copy of my c program. maybe something is wrong with my c program?
> >
> > #include "KMotionDef. h"
> >
> > #define QA 26 // define to which IO bits the AB signals are connected
> > #define QB 27
> >
> > main()
> > {
> > int BitA,Change1= 0,Change2= 0, DiffX2;
> > int PosNoWrap, NewPos, Pos=0, wraps;
> > double Factor=0;
> >
> > SetBit(152);
> > SetBit(157);
> > SetBit(158);
> >
> > ch0->InputMode= ENCODER_MODE;
> > ch0->OutputMode= DC_SERVO_ MODE;
> > ch0->Vel=100000. 000000;
> > ch0->Accel=4000000. 000000;
> > ch0->Jerk=4000000. 000000;
> > ch0->P=10.000000;
> > ch0->I=0.000000;
> > ch0->D=6.000000;
> > ch0->FFAccel= 0.000000;
> > ch0->FFVel=0. 000000;
> > ch0->MaxI=100. 000000;
> > ch0->MaxErr= 100.000000;
> > ch0->MaxOutput= 500.000000;
> > ch0->DeadBandGain= 1.000000;
> > ch0->DeadBandRange= 0.000000;
> > ch0->InputChan0= 0;
> > ch0->InputChan1= 0;
> > ch0->OutputChan0= 8;
> > ch0->OutputChan1= 1;
> > ch0->LimitSwitchOpt ions=0x8989001f;
> > ch0->InputGain0= 1.000000;
> > ch0->InputGain1= 1.000000;
> > ch0->InputOffset0= 0.000000;
> > ch0->InputOffset1= 0.000000;
> > ch0->invDistPerCycl e=1.000000;
> > ch0->Lead=0. 000000;
> > ch0->MaxFollowingEr ror=100.000000;
> > ch0->StepperAmplitu de=250.000000;
> >
> > ch0->iir[0]. B0=1.000000;
> > ch0->iir[0]. B1=0.000000;
> > ch0->iir[0]. B2=0.000000;
> > ch0->iir[0]. A1=0.000000;
> > ch0->iir[0]. A2=0.000000;
> >
> > ch0->iir[1]. B0=1.000000;
> > ch0->iir[1]. B1=0.000000;
> > ch0->iir[1]. B2=0.000000;
> > ch0->iir[1]. A1=0.000000;
> > ch0->iir[1]. A2=0.000000;
> >
> > ch0->iir[2]. B0=1.000000;
> > ch0->iir[2]. B1=0.000000;
> > ch0->iir[2]. B2=0.000000;
> > ch0->iir[2]. A1=0.000000;
> > ch0->iir[2]. A2=0.000000;
> >
> >
> >
> > EnableAxis(0) ;
> >
> > ch1->InputMode= ENCODER_MODE;
> > ch1->OutputMode= DC_SERVO_ MODE;
> > ch1->Vel=100000. 000000;
> > ch1->Accel=4000000. 000000;
> > ch1->Jerk=4000000. 000000;
> > ch1->P=10.000000;
> > ch1->I=0.000000;
> > ch1->D=6.000000;
> > ch1->FFAccel= 0.000000;
> > ch1->FFVel=0. 000000;
> > ch1->MaxI=100. 000000;
> > ch1->MaxErr= 100.000000;
> > ch1->MaxOutput= 500.000000;
> > ch1->DeadBandGain= 1.000000;
> > ch1->DeadBandRange= 0.000000;
> > ch1->InputChan0= 1;
> > ch1->InputChan1= 2;
> > ch1->OutputChan0= 9;
> > ch1->OutputChan1= 3;
> > ch1->LimitSwitchOpt ions=0x8b8b001f;
> > ch1->InputGain0= 1.000000;
> > ch1->InputGain1= 1.000000;
> > ch1->InputOffset0= 0.000000;
> > ch1->InputOffset1= 0.000000;
> > ch1->invDistPerCycl e=1.000000;
> > ch1->Lead=0. 000000;
> > ch1->MaxFollowingEr ror=100.000000;
> > ch1->StepperAmplitu de=250.000000;
> >
> > ch1->iir[0]. B0=1.000000;
> > ch1->iir[0]. B1=0.000000;
> > ch1->iir[0]. B2=0.000000;
> > ch1->iir[0]. A1=0.000000;
> > ch1->iir[0]. A2=0.000000;
> >
> > ch1->iir[1]. B0=1.000000;
> > ch1->iir[1]. B1=0.000000;
> > ch1->iir[1]. B2=0.000000;
> > ch1->iir[1]. A1=0.000000;
> > ch1->iir[1]. A2=0.000000;
> >
> > ch1->iir[2]. B0=1.000000;
> > ch1->iir[2]. B1=0.000000;
> > ch1->iir[2]. B2=0.000000;
> > ch1->iir[2]. A1=0.000000;
> > ch1->iir[2]. A2=0.000000;
> >
> > EnableAxis(1) ;
> >
> > ch2->InputMode= ENCODER_MODE;
> > ch2->OutputMode= DAC_SERVO_ MODE;
> > ch2->Vel=850. 000000;
> > ch2->Accel=50000000 .000000;
> > ch2->Jerk=50000000. 000000;
> > ch2->P=225.000000;
> > ch2->I=0.000000;
> > ch2->D=225.000000;
> > ch2->FFAccel= 0.000000;
> > ch2->FFVel=0. 000000;
> > ch2->MaxI=100. 000000;
> > ch2->MaxErr= 100.000000;
> > ch2->MaxOutput= 2047.000000;
> > ch2->DeadBandGain= 1.000000;
> > ch2->DeadBandRange= 0.000000;
> > ch2->InputChan0= 2;
> > ch2->InputChan1= 2;
> > ch2->OutputChan0= 0;
> > ch2->OutputChan1= 1;
> > ch2->LimitSwitchOpt ions=0x0;
> > ch2->InputGain0= -1.000000;
> > ch2->InputGain1= 1.000000;
> > ch2->InputOffset0= 0.000000;
> > ch2->InputOffset1= 0.000000;
> > ch2->invDistPerCycl e=1.000000;
> > ch2->Lead=0. 000000;
> > ch2->MaxFollowingEr ror=10000000. 000000;
> > ch2->StepperAmplitu de=250.000000;
> >
> > ch2->iir[0]. B0=1.000000;
> > ch2->iir[0]. B1=0.000000;
> > ch2->iir[0]. B2=0.000000;
> > ch2->iir[0]. A1=0.000000;
> > ch2->iir[0]. A2=0.000000;
> >
> > ch2->iir[1]. B0=1.000000;
> > ch2->iir[1]. B1=0.000000;
> > ch2->iir[1]. B2=0.000000;
> > ch2->iir[1]. A1=0.000000;
> > ch2->iir[1]. A2=0.000000;
> >
> > ch2->iir[2]. B0=1.000000;
> > ch2->iir[2]. B1=0.000000;
> > ch2->iir[2]. B2=0.000000;
> > ch2->iir[2]. A1=0.000000;
> > ch2->iir[2]. A2=0.000000;
> >
> > EnableAxis(2) ;
> >
> > DefineCoordSystem( 0,1,2,-1) ;
> >
> > for(;;)
> > {
> > WaitNextTimeSlice( );
> >
> > // convert quadrature to 2 bit binary
> > BitA = ReadBit(26);
> > PosNoWrap = (ReadBit(27) ^ BitA) | (BitA<<1);
> >
> > // Diff between expected position based on average of two prev deltas
> > // and position with no wraps. (Keep as X2 to avoid division by 2)
> >
> > DiffX2 = 2*(Pos-PosNoWrap) + (Change2+Change1) ;
> >
> > // Calc quadrature wraparounds to bring Diff nearest zero
> > // offset by 128 wraps to avoid requiring floor()
> > wraps = ((DiffX2+1028) >>3)-128;
> >
> > // factor in the quadrature wraparounds
> > NewPos = PosNoWrap + (wraps<<2);
> >
> > Change2 = Change1;
> > Change1 = NewPos - Pos;
> > Pos = NewPos;
> >
> > if (ReadBit(31) ) // is X1 selected?
> > Factor = 1.0;
> > else if (ReadBit(32) ) // is X100 selected?
> > Factor = 75.0;
> > else // must be X10 then
> > Factor = 10.0;
> >
> > if (ReadBit(28) ) // is x selected?
> > ch0->Dest += Change1 * Factor;
> > else if (ReadBit(29) ) // is y selected?
> > ch1->Dest += Change1 * Factor;
> > else if (ReadBit(30) ) // is z selected?
> > ch2->Dest += Change1 * Factor;
> >
> > }
> > return 0;
> > }
> >
> > --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Ryan,
> > >
> > > I have no idea why this is occurring.ÃâàCould you provide more information?ÃâàSuch as when you say everything was working then failed, what was working?ÃâàJogging or GCode motion or sitting idle?ÃâÃÂ
> > >
> > > Do you have the Keling wired up to the Aux1 connector?
> > >
> > > Possibilities I can think of might be:
> > >
> > > #1 - We don't have any protection against jogging on the MPG while GCode is running.ÃâàTo eliminate this as a possibility try re-assigning the A B Quadrature inputs to 46 and 47 (The KFlop LEDS) and see if a problem ever occurs (of course you wont be able to test jogging with the MPG).
> > >
> > > #2 - I just realized we are connecting 5V outputs to 3.3V inputs (with an internalÃâà150 ohm pull down).ÃâàÃâàI doubt if this is a problem unless the MPG is driving the signals hard above 3.9V (because the 3.3V inputs are diode clamped to the 3.3V power rail).ÃâàÃâàPlease check the outputs to see what voltage they rise to.ÃâàÃâàThe ideal test would be disconnected from the KFlop and with a 150ohm pulldown resistor.ÃâàÃâàOr add 50 ohm series resistors to be safe.
> > >
> > > #3 - Possibly just the long MPG cable picking up noise and injecting it into the system?ÃâàIs there a shield?ÃâàÃâàHow is it grounded?
> > >
> > > Sorry that is all I can think of.
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > > ____________ _________ _________ __
> > > From: bigtoy302 <bigtoy302@ ..>
> > > To: DynoMotion@yahoogro ups.com
> > > Sent: Mon, February 22, 2010 7:27:47 PM
> > > Subject: [DynoMotion] MPG problems
> > >
> > > ÃâÃÂ
> > > I am in the process of getting my system all set up. I have a Kflop, snapamp, and kanalog together. I have everything tuned and I can jog everything just fine. So I installed my Keling MPG and everything was working good for a few minutes then all the sudden the x and y servos powered off the snapamp started twitching back and forth then would fault then spin out of control. If I unplug the mpg the motors work fine. As soon as I plug it back in the freak out again. If I unplug the snapamp I can still jog the Z ( powered from the kanalog just fine)with the mpg. I am running Mach also.
> > >
> > > Ryan
> > >
> >
>
|
|
Group: DynoMotion |
Message: 213 |
From: Tom Kerekes |
Date: 3/11/2010 |
Subject: Re: MPG problems |
Hi Ryan,
You stated "changed the destinations to 5,6,7, and observed the same thing" ???
I wonder if you understood what I asked to do. Or else this is a big clue.
The idea was to change the MPG program to affect an UNUSED axis that was disabled and doesn't have any motor attached. That way when you move the mpg it should have no effect on any motor or amplifier but you should see the destination change on the screen. But did you really observe a motor move?
Maybe I wasn't clear and you also re-assigned the axes 5,6,7 to drive your motors?
Thanks
TK
Group: DynoMotion |
Message: 214 |
From: bigtoy302 |
Date: 3/11/2010 |
Subject: Re: MPG problems |
I did not switch the motors to 5,6,7, just the destinations. watching the axis scree, I could watch the counts start freaking out even though the motors where still plugged into 0,and 1. When I disconnected the motors the counts where just fine on the axis screen. Is there a phone number I could reach you at? I guess it would be better to talk to a real person so you can understand me better.
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ryan,
>
> You stated "changed the destinations to 5,6,7, and observed the same thing" ???
>
> I wonder if you understood what I asked to do. Or else this is a big clue.
>
> The idea was to change the MPG program to affect an UNUSED axis that was disabled and doesn't have any motor attached. That way when you move the mpg it should have no effect on any motor or amplifier but you should see the destination change on the screen. But did you really observe a motor move?
>
> Maybe I wasn't clear and you also re-assigned the axes 5,6,7 to drive your motors?
>
> Thanks
> TK
>
>
>
>
> ________________________________
> From: bigtoy302 <bigtoy302@...>
> To: DynoMotion@yahoogroups.com
> Sent: Thu, March 11, 2010 7:06:44 PM
> Subject: [DynoMotion] Re: MPG problems
>
> Â
> I changed the I changed the destinations to 5,6,7, and observed the same thing. I move the mpg one click(x1) and it moves the one click then states making more commands to move then faults. I left the snap amp on and the motors unplugged and it counts go up and down like they should using the mpg. As soon as try to jog it after I plugged the motors back in then restarted the system they go nuts again once I try to jog them. I a now thinking it is noise in between the snapamp and the motors. How am I supposed to ground the motors? How is the kflop and snapamp supposed to be grounded?
>
> Ryan
>
> --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> >
> > Well, connecting the mpg with power on will most likely cause the signals to toggle in unpredictable ways.ÃÂ But I'm having a hard time understanding when the problem occurs.ÃÂ Like 10 seconds after plugging in the cable?ÃÂ Or immediately?
> >
> > Disconnecting the +5V is somewhat of an invalid test.ÃÂ The signals will then probably float to invalid levels, and be highly susceptible to any noise.
> >
> > Also I don't follow your logic with removing the SnapAmp to prove it isn't a noise issue.ÃÂ As the SnapAmp may be the source of the noise.ÃÂ That was the idea behind asking you to reassign the inputs to the LEDs to elliminate that as a possibility.
> >
> > The MPG program uses some assumptions of limited acceleration to extend the count rate to ~100KHz even though the software is only looping at 5KHz.ÃÂ Basically the frequency is not expected to change instantaneously.ÃÂ If it does or changes erratically, then the algorithm can get confused and think it is moving when it is not.ÃÂ You can defeat this feature and avoid this issue (but limit your count rate to 5 KHz).ÃÂ Try changing
> >
> > Change2 = Change1;
> > Change1 = NewPos - Pos;
> >
> > to
> >
> > Change2 = 0;
> > Change1 = 0;
> >
> > Thanks
> >
> > TK
> >
> >
> >
> >
> > ____________ _________ _________ __
> > From: bigtoy302 <bigtoy302@ ..>
> > To: DynoMotion@yahoogro ups.com
> > Sent: Sun, March 7, 2010 6:34:02 PM
> > Subject: [DynoMotion] Re: MPG problems
> >
> > ÃÂ
> > I am plugging the mpg in when the the kflop and snapamp are on. Gcode is not running. I do not think I tried plugging it in then turning the power on. This may be the problem? Power spike when plugging it in? I won't have time to mess with it till Tuesday.
> >
> > To answer yout original questions:
> >
> > 1. G code not running just sitting Idle.
> > 2. I do not even have to jog it before it starts messing up. I unhooked the 5v from the mpg with the same problem.
> > 3. Un modified mpg cable plugging into a db25 connector in my control cabinet and then going to the kflop jp6. I do not think it is a noise issue because the the Z powered from the Kanalog do not mess up only the XY powered off the snapamp. The x trips first then the Y. Unplug the snapamp and I can use the mpg fine on the Z.
> >
> > On a side not I can't figure how to get my x and Y to home in mach. I have separate home and limit switches hooked up to jp12 and I can see them working in the mach screen, So that part works. I do not know what c program to use for homing and what other settings I need to set. I already modified the REF buttons in Mach like the manual said.
> >
> > Ryan
> >
> > --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> > >
> > > I can't see anything specific wrong.ÃâàYou aren't plugging in the mpg with power on or with the program running are you?ÃâàI didn't see that you answered my previous questions, but this is a big clue.ÃâàPlease change the program to change the destinations of 3 unused axis to see what happens.ÃâàTry changing:
> > >
> > > if (ReadBit(28) ) // is x selected?
> > > ch0->Dest += Change1 * Factor;
> > > else if (ReadBit(29) ) // is y selected?
> > > ch1->Dest += Change1 * Factor;
> > > else if (ReadBit(30) ) // is z selected?
> > > ch2->Dest += Change1 * Factor;
> > >
> > > To:
> > >
> > > if (ReadBit(28) ) // is x selected?
> > > ch5->Dest += Change1 * Factor;
> > > else if (ReadBit(29) ) // is y selected?
> > > ch6->Dest += Change1 * Factor;
> > > else if (ReadBit(30) ) // is z selected?
> > > ch7->Dest += Change1 * Factor;
> > >
> > > Then operate the MPG while observing the Axis Screen and Destinations 5,6,7.ÃâàDo the destinations then move as expected?ÃâàIf so, move the x,y,z motors using console commands and check if the Destinations 5,6, or 7 also somehow change.
> > >
> > > Thanks
> > > TK
> > >
> > >
> > >
> > > ____________ _________ _________ __
> > > From: bigtoy302 <bigtoy302@ ..>
> > > To: DynoMotion@yahoogro ups.com
> > > Sent: Sun, March 7, 2010 8:52:30 AM
> > > Subject: [DynoMotion] Re: MPG problems
> > >
> > > ÃâÃÂ
> > > So, played with it a little bit more and found out if I take out the mpg part of the c program I can have the mpg pluged in with no problems. But as soon as I plug the mpg in with the mpg c program loaded the x and y motors instantly get some crazy command to move then fault. I am only running the set currents for the snapamp program and thisone. Here is a copy of my c program. maybe something is wrong with my c program?
> > >
> > > #include "KMotionDef. h"
> > >
> > > #define QA 26 // define to which IO bits the AB signals are connected
> > > #define QB 27
> > >
> > > main()
> > > {
> > > int BitA,Change1= 0,Change2= 0, DiffX2;
> > > int PosNoWrap, NewPos, Pos=0, wraps;
> > > double Factor=0;
> > >
> > > SetBit(152);
> > > SetBit(157);
> > > SetBit(158);
> > >
> > > ch0->InputMode= ENCODER_MODE;
> > > ch0->OutputMode= DC_SERVO_ MODE;
> > > ch0->Vel=100000. 000000;
> > > ch0->Accel=4000000. 000000;
> > > ch0->Jerk=4000000. 000000;
> > > ch0->P=10.000000;
> > > ch0->I=0.000000;
> > > ch0->D=6.000000;
> > > ch0->FFAccel= 0.000000;
> > > ch0->FFVel=0. 000000;
> > > ch0->MaxI=100. 000000;
> > > ch0->MaxErr= 100.000000;
> > > ch0->MaxOutput= 500.000000;
> > > ch0->DeadBandGain= 1.000000;
> > > ch0->DeadBandRange= 0.000000;
> > > ch0->InputChan0= 0;
> > > ch0->InputChan1= 0;
> > > ch0->OutputChan0= 8;
> > > ch0->OutputChan1= 1;
> > > ch0->LimitSwitchOpt ions=0x8989001f;
> > > ch0->InputGain0= 1.000000;
> > > ch0->InputGain1= 1.000000;
> > > ch0->InputOffset0= 0.000000;
> > > ch0->InputOffset1= 0.000000;
> > > ch0->invDistPerCycl e=1.000000;
> > > ch0->Lead=0. 000000;
> > > ch0->MaxFollowingEr ror=100.000000;
> > > ch0->StepperAmplitu de=250.000000;
> > >
> > > ch0->iir[0]. B0=1.000000;
> > > ch0->iir[0]. B1=0.000000;
> > > ch0->iir[0]. B2=0.000000;
> > > ch0->iir[0]. A1=0.000000;
> > > ch0->iir[0]. A2=0.000000;
> > >
> > > ch0->iir[1]. B0=1.000000;
> > > ch0->iir[1]. B1=0.000000;
> > > ch0->iir[1]. B2=0.000000;
> > > ch0->iir[1]. A1=0.000000;
> > > ch0->iir[1]. A2=0.000000;
> > >
> > > ch0->iir[2]. B0=1.000000;
> > > ch0->iir[2]. B1=0.000000;
> > > ch0->iir[2]. B2=0.000000;
> > > ch0->iir[2]. A1=0.000000;
> > > ch0->iir[2]. A2=0.000000;
> > >
> > >
> > >
> > > EnableAxis(0) ;
> > >
> > > ch1->InputMode= ENCODER_MODE;
> > > ch1->OutputMode= DC_SERVO_ MODE;
> > > ch1->Vel=100000. 000000;
> > > ch1->Accel=4000000. 000000;
> > > ch1->Jerk=4000000. 000000;
> > > ch1->P=10.000000;
> > > ch1->I=0.000000;
> > > ch1->D=6.000000;
> > > ch1->FFAccel= 0.000000;
> > > ch1->FFVel=0. 000000;
> > > ch1->MaxI=100. 000000;
> > > ch1->MaxErr= 100.000000;
> > > ch1->MaxOutput= 500.000000;
> > > ch1->DeadBandGain= 1.000000;
> > > ch1->DeadBandRange= 0.000000;
> > > ch1->InputChan0= 1;
> > > ch1->InputChan1= 2;
> > > ch1->OutputChan0= 9;
> > > ch1->OutputChan1= 3;
> > > ch1->LimitSwitchOpt ions=0x8b8b001f;
> > > ch1->InputGain0= 1.000000;
> > > ch1->InputGain1= 1.000000;
> > > ch1->InputOffset0= 0.000000;
> > > ch1->InputOffset1= 0.000000;
> > > ch1->invDistPerCycl e=1.000000;
> > > ch1->Lead=0. 000000;
> > > ch1->MaxFollowingEr ror=100.000000;
> > > ch1->StepperAmplitu de=250.000000;
> > >
> > > ch1->iir[0]. B0=1.000000;
> > > ch1->iir[0]. B1=0.000000;
> > > ch1->iir[0]. B2=0.000000;
> > > ch1->iir[0]. A1=0.000000;
> > > ch1->iir[0]. A2=0.000000;
> > >
> > > ch1->iir[1]. B0=1.000000;
> > > ch1->iir[1]. B1=0.000000;
> > > ch1->iir[1]. B2=0.000000;
> > > ch1->iir[1]. A1=0.000000;
> > > ch1->iir[1]. A2=0.000000;
> > >
> > > ch1->iir[2]. B0=1.000000;
> > > ch1->iir[2]. B1=0.000000;
> > > ch1->iir[2]. B2=0.000000;
> > > ch1->iir[2]. A1=0.000000;
> > > ch1->iir[2]. A2=0.000000;
> > >
> > > EnableAxis(1) ;
> > >
> > > ch2->InputMode= ENCODER_MODE;
> > > ch2->OutputMode= DAC_SERVO_ MODE;
> > > ch2->Vel=850. 000000;
> > > ch2->Accel=50000000 .000000;
> > > ch2->Jerk=50000000. 000000;
> > > ch2->P=225.000000;
> > > ch2->I=0.000000;
> > > ch2->D=225.000000;
> > > ch2->FFAccel= 0.000000;
> > > ch2->FFVel=0. 000000;
> > > ch2->MaxI=100. 000000;
> > > ch2->MaxErr= 100.000000;
> > > ch2->MaxOutput= 2047.000000;
> > > ch2->DeadBandGain= 1.000000;
> > > ch2->DeadBandRange= 0.000000;
> > > ch2->InputChan0= 2;
> > > ch2->InputChan1= 2;
> > > ch2->OutputChan0= 0;
> > > ch2->OutputChan1= 1;
> > > ch2->LimitSwitchOpt ions=0x0;
> > > ch2->InputGain0= -1.000000;
> > > ch2->InputGain1= 1.000000;
> > > ch2->InputOffset0= 0.000000;
> > > ch2->InputOffset1= 0.000000;
> > > ch2->invDistPerCycl e=1.000000;
> > > ch2->Lead=0. 000000;
> > > ch2->MaxFollowingEr ror=10000000. 000000;
> > > ch2->StepperAmplitu de=250.000000;
> > >
> > > ch2->iir[0]. B0=1.000000;
> > > ch2->iir[0]. B1=0.000000;
> > > ch2->iir[0]. B2=0.000000;
> > > ch2->iir[0]. A1=0.000000;
> > > ch2->iir[0]. A2=0.000000;
> > >
> > > ch2->iir[1]. B0=1.000000;
> > > ch2->iir[1]. B1=0.000000;
> > > ch2->iir[1]. B2=0.000000;
> > > ch2->iir[1]. A1=0.000000;
> > > ch2->iir[1]. A2=0.000000;
> > >
> > > ch2->iir[2]. B0=1.000000;
> > > ch2->iir[2]. B1=0.000000;
> > > ch2->iir[2]. B2=0.000000;
> > > ch2->iir[2]. A1=0.000000;
> > > ch2->iir[2]. A2=0.000000;
> > >
> > > EnableAxis(2) ;
> > >
> > > DefineCoordSystem( 0,1,2,-1) ;
> > >
> > > for(;;)
> > > {
> > > WaitNextTimeSlice( );
> > >
> > > // convert quadrature to 2 bit binary
> > > BitA = ReadBit(26);
> > > PosNoWrap = (ReadBit(27) ^ BitA) | (BitA<<1);
> > >
> > > // Diff between expected position based on average of two prev deltas
> > > // and position with no wraps. (Keep as X2 to avoid division by 2)
> > >
> > > DiffX2 = 2*(Pos-PosNoWrap) + (Change2+Change1) ;
> > >
> > > // Calc quadrature wraparounds to bring Diff nearest zero
> > > // offset by 128 wraps to avoid requiring floor()
> > > wraps = ((DiffX2+1028) >>3)-128;
> > >
> > > // factor in the quadrature wraparounds
> > > NewPos = PosNoWrap + (wraps<<2);
> > >
> > > Change2 = Change1;
> > > Change1 = NewPos - Pos;
> > > Pos = NewPos;
> > >
> > > if (ReadBit(31) ) // is X1 selected?
> > > Factor = 1.0;
> > > else if (ReadBit(32) ) // is X100 selected?
> > > Factor = 75.0;
> > > else // must be X10 then
> > > Factor = 10.0;
> > >
> > > if (ReadBit(28) ) // is x selected?
> > > ch0->Dest += Change1 * Factor;
> > > else if (ReadBit(29) ) // is y selected?
> > > ch1->Dest += Change1 * Factor;
> > > else if (ReadBit(30) ) // is z selected?
> > > ch2->Dest += Change1 * Factor;
> > >
> > > }
> > > return 0;
> > > }
> > >
> > > --- In DynoMotion@yahoogro ups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Ryan,
> > > >
> > > > I have no idea why this is occurring.ÃÆ'ââ¬Å¡ÃâàCould you provide more information?ÃÆ'ââ¬Å¡ÃâàSuch as when you say everything was working then failed, what was working?ÃÆ'ââ¬Å¡ÃâàJogging or GCode motion or sitting idle?ÃÆ'ââ¬Å¡ÃâÃÂ
> > > >
> > > > Do you have the Keling wired up to the Aux1 connector?
> > > >
> > > > Possibilities I can think of might be:
> > > >
> > > > #1 - We don't have any protection against jogging on the MPG while GCode is running.ÃÆ'ââ¬Å¡ÃâàTo eliminate this as a possibility try re-assigning the A B Quadrature inputs to 46 and 47 (The KFlop LEDS) and see if a problem ever occurs (of course you wont be able to test jogging with the MPG).
> > > >
> > > > #2 - I just realized we are connecting 5V outputs to 3.3V inputs (with an internalÃÆ'ââ¬Å¡Ãâà150 ohm pull down).ÃÆ'ââ¬Å¡ÃâàÃÆ'ââ¬Å¡ÃâàI doubt if this is a problem unless the MPG is driving the signals hard above 3.9V (because the 3.3V inputs are diode clamped to the 3.3V power rail).ÃÆ'ââ¬Å¡ÃâàÃÆ'ââ¬Å¡ÃâàPlease check the outputs to see what voltage they rise to.ÃÆ'ââ¬Å¡ÃâàÃÆ'ââ¬Å¡ÃâàThe ideal test would be disconnected from the KFlop and with a 150ohm pulldown resistor.ÃÆ'ââ¬Å¡ÃâàÃÆ'ââ¬Å¡ÃâàOr add 50 ohm series resistors to be safe.
> > > >
> > > > #3 - Possibly just the long MPG cable picking up noise and injecting it into the system?ÃÆ'ââ¬Å¡ÃâàIs there a shield?ÃÆ'ââ¬Å¡ÃâàÃÆ'ââ¬Å¡ÃâàHow is it grounded?
> > > >
> > > > Sorry that is all I can think of.
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > >
> > > > ____________ _________ _________ __
> > > > From: bigtoy302 <bigtoy302@ ..>
> > > > To: DynoMotion@yahoogro ups.com
> > > > Sent: Mon, February 22, 2010 7:27:47 PM
> > > > Subject: [DynoMotion] MPG problems
> > > >
> > > > ÃÆ'ââ¬Å¡ÃâÃÂ
> > > > I am in the process of getting my system all set up. I have a Kflop, snapamp, and kanalog together. I have everything tuned and I can jog everything just fine. So I installed my Keling MPG and everything was working good for a few minutes then all the sudden the x and y servos powered off the snapamp started twitching back and forth then would fault then spin out of control. If I unplug the mpg the motors work fine. As soon as I plug it back in the freak out again. If I unplug the snapamp I can still jog the Z ( powered from the kanalog just fine)with the mpg. I am running Mach also.
> > > >
> > > > Ryan
> > > >
> > >
> >
>
|
|
| | | | | | | | | | | | | |